Re: [CMake] HOWTO cmake compatiblity?

2017-08-09 Thread Steffen Dettmer
Hi, > > > So far I think we need to install cmake into a versionized > > > directory and invoke it: I tested with versionized directory and it works really well. For example when having a symlink /opt/toolchain/1.0.0/bin/cmake -> /opt/cmake/3.6.2/bin/cmake it can be used as: $ export

Re: [CMake] HOWTO cmake compatiblity?

2017-08-07 Thread Steffen Dettmer
On Mon, Aug 7, 2017 at 3:44 PM, Rolf Eike Beer wrote: > Steffen Dettmer wrote: >> So far I think we need to install cmake into a versionized >> directory and invoke it: >> >> v1.0.0/bin/cmake -DTOOLCHAIN=v1.0.0/target1.cmake >> >> and maybe remove cmake from PATH to ensure a

Re: [CMake] HOWTO cmake compatiblity?

2017-08-07 Thread Rolf Eike Beer
Steffen Dettmer wrote: […] So far I think we need to install cmake into a versionized directory and invoke it: v1.0.0/bin/cmake -DTOOLCHAIN=v1.0.0/target1.cmake and maybe remove cmake from PATH to ensure a failure if accidentally calling "cmake". What do you think? Having multiple

[CMake] HOWTO cmake compatiblity?

2017-08-07 Thread Steffen Dettmer
Hi, I like to learn how you use cmake in environments were reproducibility is an issue. Background: We are used to simply install cmake in default $PATH, but I noticed cmake is not backward-compatible. Of course this is not surprising, it is really complex with many nice features and of