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

Alexander Neundorf neundorf at kde.org
Wed May 2 15:02:55 EDT 2018


On 2018 M05 2, Wed 09:17:53 CEST duane at duaneellis.com wrote:
> >> configure_file is not the right command
> 
> Yea, it's the nearest existing item, and it only does the most
> simplistic replacement that's why I use that as a basis for my example.
> It is in effect, like the final last 'sed' step done by gnu
> autoconfigure tools. Nothing more.
> 
> >> 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.

> 
> It's more then the IDE, it is also the CHIP effectively the SYSTEM
> 
> What I need is the variable data that Cmake has already and I need to be
> able to tell CMake that it *cannot* run the compiler instead, all of the
> information about the compiler will be provided via some Cmake script,
> for example names like this, either on the command line or specified in
> a Cmake file that holds alot of variables.
> 
>    Cmake-Embedded-${CompilerName}.txt
>    Cmake-Embedded-${ChipName}.txt
> 
> Possibly:
> 
>    Cmake-Embedded-${RtosName}.txt
> 
> or
> 
>    Cmake-Embedded-BareMetal.txt

this exists basically.
The files cmake loads are named <OS>-<tool>-<language>.cmake.
In CMake there are e.g. Generic-SDCC-C.cmake.
This would be "BareMetal" using sdcc.
You can write your own files for your own platforms.
OS and other settings can be set up in your toolchain file.

Are you familiar with cmake cross-compiling support in CMake ?
If not, please get into this, it handles many of the issues you have.

Alex



More information about the cmake-developers mailing list