[CMake] Change project name based on architecture

I have a project where I manage multiple architectures and switch back and forth frequently for testing. Full disclosure, I'm using Visual Studio. And since I cannot generate a single solution with multiple architectures (per everything I've found searching Google and the mailing list), I have two

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-456-gd6ef59f

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20161103) +set(CMake_VERSION_PATCH 20161104) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] CPACK WIX shortcuts

Yup that did it! Thanks! On Thu, Nov 3, 2016 at 12:10 PM, Nils Gladitz wrote: > On 03.11.2016 19:32, Tiago Macarios wrote: > >> >> >> And I am building it like so: >> mkdir build >> cd build >> cmake .. >> cmake --build . --config Release >> cpack -G WIX >> > > You are

[cmake-developers] Visual Studio Project Upgrade Prompt

Hi, When opening projects in the Visual Studio IDE that are using an older toolset version (ie. a VS 2012 project under VS 2015) for the first time, a prompt is displayed asking if you'd like to upgrade the projects to the newer version of Visual Studio. This gets annoying pretty quickly when

[CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

I opened a project in cmake-gui using the open project button from a vc 2010 build of a project. The open project opened the project in Visual Studio 2010. Later I opened the same project but a different build tree for Visual Studio 2013 CMake-gui had all of the correct information for the Visual

Re: [CMake] CPACK WIX shortcuts

On 03.11.2016 19:32, Tiago Macarios wrote: And I am building it like so: mkdir build cd build cmake .. cmake --build . --config Release cpack -G WIX You are using a multi-configuration generator (Visual Studio). As you do in the build try specifying a configuration to be packaged when

Re: [CMake] CPACK WIX shortcuts

Hi Nils, Here are all the versions of things involved: Windows10 1607 14393.351 cmake 3.6.3 wix 3.10.3 VS 2015 Update 3 14.0.25431.01 I modified the test to be self contained: == cmake_minimum_required(VERSION 3.6) add_executable(h-w hw.cpp)

[CMake] [ANNOUNCE] CMake 3.6.3 available for download

We are pleased to announce that CMake 3.6.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.6.3 since 3.6.2: Brad

Re: [CMake] Building CMake without Curl

It looks like you're using an existing configuration already set to use system installed libraries. Try from a clean source tree and an out-of-source (the recommend way to do all cmake things) build directory. Using the 3.6.2 tarball, I get: $ tar -xvf cmake-3.6.2.tar.gz ... lots of tar output

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-935-gcec11d1

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-455-g60d80bc

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

[Cmake-commits] CMake annotated tag, v3.6.3, created. v3.6.3

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 annotated tag, v3.6.3 has been created at a2f08cbcf890eddf45e3de50a05b97764d841ae3 (tag) tagging

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-933-g0e78a19

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-930-gf4570ad

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-928-g54eed9a

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-453-gdec0cfc

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-926-ga279f93

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

[Cmake-commits] CMake branch, release, updated. v3.7.0-rc2-36-g5f7f0ab

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, release has been updated via 5f7f0ab517d9f4fbc11292a1bada37a74ba69b97 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-448-gacc2e03

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-444-ge106a6e

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-446-g3dd9975

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-920-g5b24b80

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-436-g90e09fb

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-914-g17c1cb1

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-912-gefb4160

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

Re: [cmake-developers] Add property to get all linked libraries including transitive ones

On 11/02/2016 04:23 PM, maikel van den Hurk wrote: > We are trying to develop a proper C++ dependency management tool > ...be able to get all transitive linked libraries The cmake-server mode introduced in 3.7 was created to support tooling. Perhaps something with that can be made to work if it

Re: [CMake] CPACK WIX shortcuts

On 11/03/2016 12:23 AM, Tiago Macarios wrote: Hi, I am trying to create an installer with CPACK and WIX as generator. Everything works fine except that I cannot get start menu shortcuts to work. I was using almost the same code as the link below (which seems to be the unit tests for this