[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-143-g9f7a232

2016-02-25 Thread Kitware Robot
_VERSION_MINOR 5) -set(CMake_VERSION_PATCH 20160225) +set(CMake_VERSION_PATCH 20160226) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] Windows 10 Store App - deploy content

2016-02-25 Thread Gilles Khouzam
We have a pull request on our branch that might be helpful by make them extensions. https://github.com/Microsoft/CMake/pull/15 From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Thursday, February 25, 2016 07:48 To: cmake-developers@cmake.org; Gilles Khouzam

[CMake] check_cxx_compiler_flag fails silently for complex compiler paths

2016-02-25 Thread Andrew Hundt
I believe check_cxx_compiler_flags is failing due to a long/complicated compiler path. Specifically my compiler is set to: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ CMake version: 3.4.3 Full trace output in gist where you can see lines warning of

Re: [CMake] ExternalProject_Add with flexible install commands

2016-02-25 Thread Knox, Kent
I don't need to use indirection, but the reason I decided to try was to simplify my code. I could either wrap the ExternalProject_Add() call in a branch/switch or a single set() call. I am using your 'hack' thusly: set( libxxx_inst_comm INSTALL_COMMAND ${CMAKE_COMMAND} -E echo_append ) and

Re: [cmake-developers] [PATCH] Add target property VS_CONFIGURATION_TYPE to Visual Studio 10 target generator

2016-02-25 Thread Brad King
On 02/25/2016 10:36 AM, fabian.o...@rohde-schwarz.com wrote: > thanks for your feedback. I added a test for the feature. Thanks. It looks like your mailer mangled the original patch. Please re-send both patches as attachments. Thanks, -Brad -- Powered by www.kitware.com Please keep messages

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-291-gca566cd

2016-02-25 Thread Joe Snyder
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 ca566cd242b363f43e313ab9cd16f9521db8fc7b (commit) via

[cmake-developers] [CMake 0015988]: No parse error message on double 'else' contruction

2016-02-25 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15988 == Reported By:Ruslan Baratov Assigned To:

Re: [CMake] ExternalProject_Add with flexible install commands

2016-02-25 Thread David Cole via CMake
Do you need to do it indirectly through a variable like this? If you just use: INSTALL_COMMAND "" directly in the ExternalProject_Add call, it will work. If you really need to do it indirectly, there's probably a way, but it will also probably be more confusing for people reading the code in

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-289-gdd6870d

2016-02-25 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 dd6870d0dab8ede1a2861016f052897f26541919 (commit) via

Re: [CMake] ExternalProject_Add with flexible install commands

2016-02-25 Thread Knox, Kent
Hi Petr~ Thanks for your reply. These set statements do not appear to work. Either the command 'installs' the dependency, or an error pops up. set( rocblas_INSTALL_COMMAND INSTALL_COMMAND "" ) --> this installs the dependency set( rocblas_INSTALL_COMMAND INSTALL_COMMAND " " ) --> /bin/sh:

Re: [CMake] cmake documentation incomplete

2016-02-25 Thread Nicholas Braden
I don't know about -B, but you can take advantage of the tool mode like this: cmake -E chdir path/to/build cmake [options] path/to/source Effectively you can use the chdir tool to spawn CMake with the working directory you want it to have. On Thu, Feb 25, 2016 at 9:37 AM, Vania Joloboff

Re: [CMake] cmake documentation incomplete

2016-02-25 Thread Vania Joloboff
Thanks Nicholas, Then if I run cmake from a shell script in working directory pwd (and I do not want to cd) can I tell cmake the first time to take the source in path-to-source and do the build in path-to-build ? I have read there is an undocumented option -B to do this ? Vania On 02/25/2016

Re: [cmake-developers] [PATCH] Add target property VS_CONFIGURATION_TYPE to Visual Studio 10 target generator

2016-02-25 Thread Fabian . Otto
Hi Brad, thanks for your feedback. I added a test for the feature. Best regards, Fabian --- Tests/RunCMake/CMakeLists.txt | 5 + Tests/RunCMake/VS10Project/CMakeLists.txt | 3 +++ Tests/RunCMake/VS10Project/RunCMakeTest.cmake | 2 ++

Re: [CMake] cmake documentation incomplete

2016-02-25 Thread Nicholas Braden
Yes, an existing build saves all the information it needs in the build cache. Once you have created a build, you never need to specify the source directory again. On Thu, Feb 25, 2016 at 9:13 AM, Vania Joloboff wrote: > Hi, > > The cmake documentation says there are two

Re: [CMake] cmake documentation incomplete

2016-02-25 Thread Vania Joloboff
Hi, The cmake documentation says there are two alternatives to start cmake cmake [] ( | ) But it does not explain nowhere the difference between the two... Does the path-to-existing-build retrieve itself the source dir and start like if it were invoked with path-to-source from

[CMake] file(SHA1) vs string(SHA1) consistency

2016-02-25 Thread Ruslan Baratov via CMake
Hi, Following code produce same SHA1 on Linux: cmake_minimum_required(VERSION 3.0) set(test_string "a\nb") set(test_file "test.file") string(SHA1 sha1_string "${test_string}") file(WRITE "${test_file}" "${test_string}") file(SHA1 "${test_file}" sha1_file)

[cmake-developers] [CMake 0015987]: STATUS variable to FILE(DOWNLOAD) does not consider HASH mismatch failures

2016-02-25 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15987 == Reported By:Tobias Hieta Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-287-g5aa7416

2016-02-25 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 5aa7416f9bebe43aa98d8ff66e416721706ecbd5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-142-gf8af218

2016-02-25 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 f8af218ea148baafcfc3db6ea5ba7389f5ea7206 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-140-gc842411

2016-02-25 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 c842411dc5a2123cdc9d949b67f8421379a4a928 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-137-gdd99bff

2016-02-25 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 dd99bfff3a25668c2043e776d775f7ebaef82d03 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-283-ge2b8af5

2016-02-25 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 e2b8af58c0f4e497bd9a557a8eac7c53f974640a (commit) via

Re: [cmake-developers] C# support ready for review

2016-02-25 Thread Stuermer, Michael SP/HZA-ZSEP
Hi Gilles, good to hear C# support is working not only for me and some people are actually interested in it :-). Thanks for the patch, I already added to my github. All the changes make perfectly sense for me. Let me explain a bit more about things like hardcoding LangVersion in the module

Re: [CMake] ExternalProject_Add with flexible install commands

2016-02-25 Thread Petr Kmoch
Hi Kent, I believe it's not "empty quotes" that disables the install command, it's the empty string. So you should not escape the quotes: ### # Default behavior is to NOT install library, empty quotes should disable install set( libxxx_inst_comm INSTALL_COMMAND "" ) # Build

[CMake] ExternalProject_Add with flexible install commands

2016-02-25 Thread Knox, Kent
I am having a problem passing parameters as a variable into ExternalProject_Add(). I seem to be fighting syntax, i've tried many different variants with the set() statement ### # Default behavior is to NOT install library, empty quotes should disable install set(