[cmake-developers] new generator question - xml file output for embedded IDE platforms.

[duane at duaneellis.com]

> > >> If an IDE is actually not supported by CMake a generator it will have to
> > >> be implemented for that in the source code of CMake.
> > yea, i'm trying to avoid that - but I can write that if required :-(

> I think you'll have to do this.

Hmm - Another approach is to use Python to create the IDE files
And from that python script generate CMakefiles for the unit test
situation.

Sort of backwards from where I am starting, but that said - my focus is
the Embedded side, not the host.

One thing that is never easy is a "split language" development
environment. ie:  Some stuff is done in C (the generator) - and some
stuff is done in Script (ie: Cmake Language)
you don't have a debugger for Cmake, just print statements, and  you are
always asking your self the question: "Should this step be in Language
A, or Language B"


>> {duane: Various cmake examples, snip snip }
>> Cmake-Embedded-${CompilerName}.txt
>> Cmake-Embedded-${ChipName}.txt
>> Cmake-Embedded-${RtosName}.txt
>> Cmake-Embedded-BareMetal.txt

> this exists basically.
> [snip]
>In CMake there are e.g. Generic-SDCC-C.cmake.

but that uses/requires/assumes - Make files are used to run the build.
Having the IDE execute Make - while doable, is *NOT* desired.

>> Are you familiar with cmake cross-compiling support in CMake ? 

yes, I'm currently building Cmake from source, and stepping through the
code experimenting and learning how Generators work.
For my generator I basically need to make a dummy (does nothing)
generator and let everything be done in the template

Often it seems to always comes back to the generator and what needs to
be done there.  It is same problem I talked about earlier - some things
are in CmakeScript, Some are in C, and others will be in the template it
self, and where does feature(X) need to be in C, or in Cmake or in the
Template?

-Duane.