Re: [CMake] Wrap CACHE variables

Have you considered having a superbuild and using ExternalProject_Add to build the dependencies? http://www.cmake.org/cmake/help/v3.1/module/ExternalProject.html Excellent examples of using ExternalProject for a superbuild live in the OpenChemistry and Slicer projects.

[Cmake-commits] CMake branch, master, updated. v3.1.0-636-gbc04555

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 bc04b54734fa20a69d87d64ae9152639654d (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-634-g427d932

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 427d9324983ddd02d5afff780c6b23ab5081c8df (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1641-g5b47c32

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 5b47c32a9d7a67fadd904a4f41c4838eb79a04c2 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1637-g7276bd8

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 7276bd8fc3bf055c27e34751c3df052a3ba42a8e (commit) via

[CMake] NSIS startup menu and icons

I have created an NSIS section for my CMakeLists.txt and I am trying to pack and install my application (mrViewer). The package builds correctly and runs just fine, but the mrViewer icon is missing in desktop and in the menu entry and the startup menu has a mrViewer entry that leads nowhere

Re: [CMake] NSIS builder creating invalid exe

On 09/01/15 19:22, Bill Hoffman wrote: On 1/9/2015 12:43 PM, Gonzalo Garramuño wrote: I updated my CMakeLists.txt to create an NSIS installer under a Nmake Makefile. The packaging works without errors when run with 'nmake package'. However, the resulting exe file when run, returns: Bad file

[Cmake-commits] CMake branch, next, updated. v3.1.0-1629-g761bc9f

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 761bc9f27850eb9425d8d222a3312007cdc24908 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1631-g8504583

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 85045836c29eaa58efdb4c01aeb62d3b44290cac (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1634-gd388bda

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 d388bda78fb01e6a8cebad0464cd7b9eefd91eef (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1645-g0144470

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 0144470b71bd9c1d0ec138ebda9cb28d8b762009 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1647-g57e8b86

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 57e8b86866517c1fdc75b93fdc03b791247f95dd (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-1649-gc7fb8d3

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 c7fb8d364b6915cd603573fdfb4670c88d728050 (commit) via

[cmake-developers] [PATCH] Document find_package CMAKE_FIND_PACKAGE_NAME variable

Signed-off-by: Gregor Jasny gja...@googlemail.com --- Help/command/find_package.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Help/command/find_package.rst b/Help/command/find_package.rst index 190d05c..7f518a6 100644 --- a/Help/command/find_package.rst +++

Re: [cmake-developers] Extracting target metadata, IDE integration

Aleix Pol wrote: I'll attach it in this e-mail, to make sure it reaches. PS: there's no changes system for cmake like reviewboard, is there? Nope, review is communicated on the mailing list, but if you want you can push the patch on a branch in a public repo. It could be more convenient.

Re: [cmake-developers] Which binaries should be required in FindLATEX?

Hi Brad, concerning FindLATEX again: Applied: FindLATEX: Add components handling http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=07a3f9ad The link does not work and I couldn't find the commit in next. Can you double check whether you pushed it? with minor documentation tweaks and one

[Cmake-commits] CMake branch, next, updated. v3.1.0-1643-gf1fa6eb

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 f1fa6eb9c12d28f0d5e6afa23e012856238cfc6b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-637-g7e5e8a3

20150110) +set(CMake_VERSION_PATCH 20150111) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake