Re: [cmake-developers] Add a new SYSTEM_ONLY mode for CMAKE_FIND_ROOT_PATH

2014-08-20 Thread Brad King
On 08/19/2014 05:43 PM, Chuck Atkins wrote: The new hybrid mode allows the default search location to be re-rooted and any user specified paths to be untouched. This looks useful. However, the current implementation appears to change the order in which each kind of path is generated. The order

Re: [cmake-developers] Add a new SYSTEM_ONLY mode for CMAKE_FIND_ROOT_PATH

2014-08-20 Thread Chuck Atkins
I was trying to avoid the code duplication but I definitely see your point. I'll refactor. - Chuck On Wed, Aug 20, 2014 at 8:55 AM, Brad King brad.k...@kitware.com wrote: On 08/19/2014 05:43 PM, Chuck Atkins wrote: The new hybrid mode allows the default search location to be re-rooted

Re: [cmake-developers] Add a new SYSTEM_ONLY mode for CMAKE_FIND_ROOT_PATH

2014-08-20 Thread Chuck Atkins
The branch has been updated on the stage to retain search path order. - Chuck On Wed, Aug 20, 2014 at 9:10 AM, Chuck Atkins chuck.atk...@kitware.com wrote: I was trying to avoid the code duplication but I definitely see your point. I'll refactor. - Chuck On Wed, Aug 20, 2014 at 8:55

Re: [CMake] Collecting libraries for NSIS installer

2014-08-20 Thread Richard Shaw
On Tue, Aug 19, 2014 at 11:40 AM, Hendrik Sattler p...@hendrik-sattler.de wrote: On 19. August 2014 16:36:14 MESZ, David Cole via CMake cmake@cmake.org wrote: Definitely getting warmer! It looks like that GetPrerequistes only works on an existing target so I'm thinking I would have to set

Re: [CMake] Collecting libraries for NSIS installer

2014-08-20 Thread David Cole via CMake
Yes, the more I look at this the more I realize it's not going to work. The script method is going to install the required libraries, in my case on win32 no one is going to run make install it's instead going to be make package. But make package typically runs make install under the hood...

[CMake] organizing export link libraries

2014-08-20 Thread Nico Schlömer
Hi all, a general question: I have a dependency chain of libraries A - B - C - ... - Z and all of those libraries are built with CMake, using CMake's export functionality [1] to let the next in the chain know about its the dependencies. If all of the libraries are built statically and A needs

Re: [CMake] Variable shadowing between scope, cache and command line argument

2014-08-20 Thread Alexander Neundorf
On Wednesday, July 30, 2014 14:59:46 Ghyslain Leclerc wrote: Hello, First post here. Sorry if its too long. Simply trying to be as clear as I can be. I am trying to make sense of the various ways to set a variable and how one can shadow the other. Long story short, I am trying to get

Re: [CMake] Collecting libraries for NSIS installer

2014-08-20 Thread Richard Shaw
Ok, that being the case I tried it out. There's two things I'm doing differently than the only example[1] I found: 1. Using install(CODE...) instead of install(SCRIPT...), shouldn't work any differently, right? 2. The example is from 2009 and uses: GET_TARGET_PROPERTY(MY_BINARY_LOCATION

Re: [CMake] How to deal with incompatible changes in interface of target_link_libraries()?

2014-08-20 Thread Alexander Neundorf
On Tuesday, August 12, 2014 09:06:13 Brad King wrote: ... FYI, the only intended use case for setting a policy to OLD is to quiet warnings in a maintenance branch of an existing release. Some day support for OLD behavior of some policies may be dropped, so all project development moving

Re: [CMake] Collecting libraries for NSIS installer

2014-08-20 Thread Richard Shaw
Ok, short answer to #1, no you can't use install(CODE because all your cmake variables we be evaluated now instead of later. Same problem though when I use install(SCRIPT... Run CPack packaging tool... CPack: Create package using NSIS CPack: Install projects CPack: - Run preinstall target for:

[Cmake-commits] CMake branch, next, updated. v3.0.1-4983-gf13f913

2014-08-20 Thread Brad King
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, next has been updated via f13f913f7cbde7616e2a2fc2209e087967ecba58 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-4985-gbc419fa

2014-08-20 Thread Brad King
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, next has been updated via bc419fa05ee44b12ace8db8dd1eab1615eaf82d4 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-4987-g6e35477

2014-08-20 Thread Brad King
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, next has been updated via 6e354771a8f8a7ec95e878eb658a56800b6c8639 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.1-1735-g16afcca

2014-08-20 Thread Brad King
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 16afccac0542cff1ee440eaa77512ba35223ea78 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-4990-gd963457

2014-08-20 Thread Brad King
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, next has been updated via d963457e4425185f3235c950538bd4056959889c (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.1-1736-g4517d6b

2014-08-20 Thread Kitware Robot
20140820) +set(CMake_VERSION_PATCH 20140821) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake