Andrey Pokrovskiy wrote:
Hi,
I'm using cmake and CMAKE_TOOLCHAIN_FILE to build the project and it's
dependencies. Some toolchain files have additional options (like API
version, target architecture, linker type, etc.) which you need to
pass to cmake command with -D in addition to the
On 04/26/2015 09:08 PM, David Cole via cmake-developers wrote:
I really don't see how you solve the problem by having a toolchain
file and some arbitrary set of variables to be passed down. Either you
have to put the CMAKE_TOOLCHAIN_ARGS into the toolchain file itself,
or you have to specify
Hi,
I'm using cmake and CMAKE_TOOLCHAIN_FILE to build the project and it's
dependencies. Some toolchain files have additional options (like API
version, target architecture, linker type, etc.) which you need to
pass to cmake command with -D in addition to the
-DCMAKE_TOOLCHAIN_FILE= itself.
So
Because it will be an ad-hoc solution. Also each time I will start
using a new toolchain file (for another device/platform) I will need
to modify that wrapper script. And each time I will override some
toolchain variable I will need to look into that wrapper to verify
that this variable will be
I realize that sometimes dependencies are necessary.
But.
There's a very strong argument to be made that projects should not
have a lot of external dependencies.
If you really need to tell an ExternalProject build this external
project the same way as the main one, you should probably write
