kicad-developers team mailing list archive
Mailing list archive
Re: Eeschema Default Library Field Names
Wayne Stambaugh <stambaughw@...>
Tue, 09 Mar 2010 10:30:32 -0500
Thunderbird 220.127.116.11 (Windows/20090812)
Dick Hollenbeck wrote:
> Dick Hollenbeck wrote:
>> It is probably only a 1/2 day's work, and half that is figuring out how
>> to tell CMake to build this tool natively, (even in a cross compiler
>> environment) and to invoke the tool in the proper way AFTER IT IS BUILT,
>> natively. CMake can do this, I know, but some reading is probably
>> It should be fun for somebody, and I have no doubt you'd do it
>> exceptionally well Wayne.
> As an alternative to C++, a reasonable choice would also be CMake
> itself. The "list" operations are probably powerful enough to get the
> job done.
> My CMakeModules/Html2C.cmake could serve as an example.
> I do not have a preference on C++ vs. Cmake script.
Thanks for all of the input. I'll probably try implementing it as a
CMake macro first and fall back to C++ if I'm not satisfied with the
results. CMake has decent string and regular expression support so it
may be a better solution for cross compiling. It may be a while before
I can take a look at it as my main desktop computer at home is in the
process of being rebuilt thanks in large part to an operating system
that shall remain nameless. I am seriously considering making it a
Linux only machine and letting the family fend for themselves on the
> Each has its advantages here. C++ is a better foundation if we ever
> wanted to take it further, such as recursive code generation.
> CMake is easier to make in view of cross compilation support.