That mechanism sort of exists through Toolchain files:
https://cmake.org/cmake/help/v3.0/manual/cmake-toolchains.7.html
CMake ships with numerous platforms -- look in Modules/Platform of your
installation directory for examples -- and you can create and ship a set of
toolchain files for your p
Chuck, Tim:
Thank you both for the help. I'll give these ideas a try and see how they shake
out.
The "module" command is a new one to me. Looks like it can be helpful for a
variety of tasks.
I do still wish cmake had a method to select a tool family that was:
1) Succinct (i.e. short to type)
> when I place set(CMAKE_SYSTEM_NAME Generic) after cmake_minimum_required()
> and project() and set(VERSION_MAYOR/MINOR),
>
CMAKE_SYSTEM_NAME really shouldn't be in a CMakeLists.txt file at all. It
should instead be in a stand alone toolchain file defining your various
cross-compiling requiremen
Hi,
when I place set(CMAKE_SYSTEM_NAME Generic) after cmake_minimum_required()
and project() and set(VERSION_MAYOR/MINOR), incremental „make“s still work,
but once the build directory is cleared and „cmake ..“ is invoked, „make“
always leads to the error „avr-gcc: error: unrecognized command line
