Re: [CMake] absolute library path, sorry for the question

2017-12-23 Thread Alan W. Irwin
On 2017-12-23 10:47+0100 Andreas Naumann wrote: your problem is hard to analyse. If you have a "minimal" example, which shows this behavior, we could test it. In your last mail, you wrote about building and installing libtiff using your own libjpeg. But than you write about a later build. So

Re: [CMake] ExternalProject_Add and Git Update? How do I make these work?

2017-12-23 Thread Kris Thielemans
Hi The strange thing here is Cannot rebase: You have unstaged changes. Please commit or stash them. No rebase in progress? Why would it be rebasing? Maybe a local config setting that a pull is always pull --rebase? In any case, my guess is that your discount/Source is in a funny state compare

Re: [CMake] absolute library path, sorry for the question

2017-12-23 Thread Andreas Naumann
your problem is hard to analyse. If you have a "minimal" example, which shows this behavior, we could test it. In your last mail, you wrote about building and installing libtiff using your own libjpeg. But than you write about a later build. So something must happen in the "later build".

[CMake] how to add a test that calls ctest

2017-12-23 Thread Kris Thielemans
Hi We have a superbuild-type project https://github.com/CCPPETMR/SIRF-SuperBuild where we want to add tests that call ctest for the dependent projects. We do this as COMMAND ${CMAKE_CTEST_COMMAND} WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/SIRF-prefix/src/SIRF-build/)

Re: [CMake] absolute library path, sorry for the question

2017-12-23 Thread Bo Zhou
https://cmake.org/cmake/help/v3.0/command/find_path.html Please try to pass the NO_CMAKE_SYSTEM_PATH to find_path() and find_library(), but use the HINT to pass the path to thirdparty paths. Of course use the CMAKE_VERBOSE_MAKEFILE to check the log. At the last check the CMakeCache.txt to

[Cmake-commits] CMake branch, master, updated. v3.10.1-690-g0d22a23

2017-12-23 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 0d22a23fd2382320907d8d3b97d8784281c40681 (commit) via

Re: [cmake-developers] CMP0022 documentation is outdated

2017-12-23 Thread Alan W. Irwin
On 2017-12-19 14:18-0800 Alan W. Irwin wrote: I have a software project with a dated CMake-based build system that specifically set CMP0022 to OLD. So while updating that build system I naturally consulted the latest CMP0022 documentation, e.g.,

Re: [cmake-developers] CMP0022 documentation is outdated

2017-12-23 Thread Domen Vrankar
2017-12-23 13:25 GMT+01:00 Alan W. Irwin : > On 2017-12-19 14:18-0800 Alan W. Irwin wrote: > > I have a software project with a dated CMake-based build system that >> specifically set CMP0022 to OLD. So while updating that build system >> I naturally consulted the

Re: [cmake-developers] CMP0022 documentation is outdated

2017-12-23 Thread Alan W. Irwin
On 2017-12-24 00:01+0100 Domen Vrankar wrote: 2017-12-23 13:25 GMT+01:00 Alan W. Irwin : [...] So I guess the conclusion is it's a very low priority to update the documentation of ancient policies like this one. I guess that's fine if the plan is these ancient

[Cmake-commits] CMake branch, master, updated. v3.10.1-691-g40dea7e

2017-12-23 Thread Kitware Robot
VERSION_MINOR 10) -set(CMake_VERSION_PATCH 20171223) +set(CMake_VERSION_PATCH 20171224) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/