[Cmake-commits] CMake branch, master, updated. v3.8.0-859-g8b0016a

2017-04-23 Thread Kitware Robot
_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170423) +set(CMake_VERSION_PATCH 20170424) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[cmake-developers] On-going UseSWIG troubles with the official versions

2017-04-23 Thread Alan W. Irwin
On 2017-04-23 17:10+0200 Rolf Eike Beer wrote: The somewhat longer story is just at the start (fortunately for me) of that simplification process, I double checked the source of both FindSWIG.cmake and UseSWIG.cmake as used by PLplot, and those turned out to be special cutting-edge versions

Re: [cmake-developers] [UseSWIG] regression in results from CMake-3.0.2 to recent versions --SOLVED

2017-04-23 Thread Rolf Eike Beer
> The somewhat longer story is just at the start (fortunately for me) of > that simplification process, I double checked the source of both > FindSWIG.cmake and UseSWIG.cmake as used by PLplot, and those turned > out to be special cutting-edge versions recommended by one user of the > cmake bug

Re: [cmake-developers] [UseSWIG] regression in results from CMake-3.0.2 to recent versions --SOLVED

2017-04-23 Thread Alan W. Irwin
On 2017-04-22 21:46-0700 Alan W. Irwin wrote: So my next steps are gross simplification (to prove this cross-contamination of build rules for UseSWIG-generated modules in the same CMakeLists.txt file really is due to a regression in CMake somewhere between CMake-3.0.2 and 3.7.2. Note that both

Re: [cmake-developers] Where execute_process INPUT_CONTENT or INPUT_VARIABLE?

2017-04-23 Thread Konstantin Podsvirov
23.04.2017, 12:26, "Alan W. Irwin" : > On 2017-04-23 10:24+0300 Konstantin Podsvirov wrote: > >>  Hi Alan! >> >>  23.04.2017, 10:01, "Alan W. Irwin" : >>>  On 2017-04-23 08:30+0300 Konstantin Podsvirov wrote: >>>   Where execute_process

Re: [cmake-developers] Where execute_process INPUT_CONTENT or INPUT_VARIABLE?

2017-04-23 Thread Alan W. Irwin
On 2017-04-23 10:24+0300 Konstantin Podsvirov wrote: Hi Alan! 23.04.2017, 10:01, "Alan W. Irwin" : On 2017-04-23 08:30+0300 Konstantin Podsvirov wrote:  Where execute_process INPUT_CONTENT or INPUT_VARIABLE?  This would be very convenient for a small input.  Why

Re: [cmake-developers] Where execute_process INPUT_CONTENT or INPUT_VARIABLE?

2017-04-23 Thread Konstantin Podsvirov
Hi Alan! 23.04.2017, 10:01, "Alan W. Irwin" : > On 2017-04-23 08:30+0300 Konstantin Podsvirov wrote: > >>  Where execute_process INPUT_CONTENT or INPUT_VARIABLE? >> >>  This would be very convenient for a small input. >> >>  Why should I always write a file for input? >

Re: [CMake] check_c_source_compiles caching pitfalls

2017-04-23 Thread Hendrik Sattler
Am 23. April 2017 03:16:41 MESZ schrieb Tyson Nottingham : >The result of check_c_source_compiles and similar commands >(check_c_source_runs, check_cxx_source_compiles, etc.) is cached by the >variable name passed in. This caching makes those commands and ones >that