[CMake] want to store hash of binaries into install - but CPack..

2017-09-11 Thread ken poole
We are looking for a way to include a hash/binary element of our install. The target platform is linux, and we use the CPack feature that updates the RPATH in the binaries during the creation of the install. Is there any way to run a script after the binaries have had their RPATHs updated by cpack

Re: [CMake] How to maintain compatibility with earlier versions?

2017-09-11 Thread Alan W. Irwin
On 2017-09-11 18:06+0300 Konstantin Tokarev wrote: 11.09.2017, 16:52, "Robert Dailey" : So typically my setup is that I have the newest CMake installed, but am working with projects that set cmake_minimum_required to something like version 2.8. Will version 3.9 of CMake prevent me from using

Re: [CMake] [Windows] clang-cl.exe detected as MSVC?

2017-09-11 Thread Konstantin Tokarev
11.09.2017, 17:59, "Mateusz Loskot" : > Hi, > > I'm building a project with CMake 3.9 using clang-cl.exe driver [1] > from LLVM/clang 4.0 enabled with Visual Studio 2015 environment. > > CMake detects the compiler as Clang 4.0.0: > > -- The C compiler identification is Clang 4.0.0 > -- The CXX co

Re: [CMake] [Windows] clang-cl.exe detected as MSVC?

2017-09-11 Thread Mateusz Loskot
On 11 September 2017 at 17:04, Konstantin Tokarev wrote: > 11.09.2017, 17:59, "Mateusz Loskot" : >> Hi, >> >> I'm building a project with CMake 3.9 using clang-cl.exe driver [1] >> from LLVM/clang 4.0 enabled with Visual Studio 2015 environment. >> >> CMake detects the compiler as Clang 4.0.0: >>

Re: [CMake] How to maintain compatibility with earlier versions?

2017-09-11 Thread Konstantin Tokarev
11.09.2017, 16:52, "Robert Dailey" : > So typically my setup is that I have the newest CMake installed, but > am working with projects that set cmake_minimum_required to something > like version 2.8. Will version 3.9 of CMake prevent me from using > features that were introduced after 2.8? How ca

[CMake] [Windows] clang-cl.exe detected as MSVC?

2017-09-11 Thread Mateusz Loskot
Hi, I'm building a project with CMake 3.9 using clang-cl.exe driver [1] from LLVM/clang 4.0 enabled with Visual Studio 2015 environment. CMake detects the compiler as Clang 4.0.0: -- The C compiler identification is Clang 4.0.0 -- The CXX compiler identification is Clang 4.0.0 -- Check for worki

[CMake] How to maintain compatibility with earlier versions?

2017-09-11 Thread Robert Dailey
So typically my setup is that I have the newest CMake installed, but am working with projects that set cmake_minimum_required to something like version 2.8. Will version 3.9 of CMake prevent me from using features that were introduced after 2.8? How can I make sure that someone with *actual* versio