[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-243-g099f6c300a

2019-11-05 Thread Kitware Robot via Cmake-commits
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 7425c0fcdc..c8e91089da 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,7 +1,7 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 16) -set(CMake_VERSION_PATCH 2019

[CMake] cross-testing support in cmake

2019-11-05 Thread Stefan Seefeld
Hello, I'm looking for ways to enable cross-testing with cmake. I imagine some helper script that, during test execution, copies the test binary to a test platform, runs the binary there, and reports back the test result. Does cmake have support for such a scenario ? Thanks, Stefan --

[cmake-developers] [ANNOUNCE] CMake Discourse forum now available

2019-11-05 Thread Robert Maynard via cmake-developers
A Discourse forum is now available for the CMake community: https://discourse.cmake.org Discourse offers users more control over their level of participation, allowing them to subscribe or unsubscribe by category or individual topic. Users may choose to participate by web forum, email, or

[CMake] [ANNOUNCE] CMake Discourse forum now available

2019-11-05 Thread Robert Maynard via CMake
A Discourse forum is now available for the CMake community: https://discourse.cmake.org Discourse offers users more control over their level of participation, allowing them to subscribe or unsubscribe by category or individual topic. Users may choose to participate by web forum, email, or

Re: [cmake-developers] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

2019-11-05 Thread Brad King via cmake-developers
On 11/5/19 7:30 AM, Alexander wrote: > string(APPEND CMAKE_SHARED_LINKER_FLAGS " -DEF:\"foo_1.def\" > -DEF111:\"foo_1.def\"") This was the first you've mentioned using more than one copy of the flag. I tested with this: ``` string(APPEND CMAKE_SHARED_LINKER_FLAGS "

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-29-g3c0a317a1d

2019-11-05 Thread Kitware Robot via Cmake-commits
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 3c0a317a1d111fb1012de45c39b81048f5a700d9 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-242-g370fe1495b

2019-11-05 Thread Kitware Robot via Cmake-commits
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 370fe1495b4109430b2cb250dd3afd1ce9401cf6 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-234-gcb165b8b79

2019-11-05 Thread Kitware Robot via Cmake-commits
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 cb165b8b79c96a3ff6db12cb1821cfa2c0c4cce5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-224-g20fdf9a92b

2019-11-05 Thread Kitware Robot via Cmake-commits
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 20fdf9a92b2c46937353a53949636131d3664fc7 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-221-g57db062414

2019-11-05 Thread Kitware Robot via Cmake-commits
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 57db062414d0ae711a6e66c9eef69eabaa8fee6f (commit) via

[CMake] combining multiple build variants into the same package (and install prefix)

2019-11-05 Thread stefan
Hello, I'm trying to repackage an upstream project that's using CMake. The project is set up to allow me to specify whether to build shared or static libs using the BUILD_SHARED_LIBS when invoking cmake. However, rather than generating two separate packages for the two variants, I'd like to

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-219-gb089396f8e

2019-11-05 Thread Kitware Robot via Cmake-commits
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 b089396f8e60c7a4a9e5fbece8484e7e77fd503a (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-18-gc831e409a5

2019-11-05 Thread Kitware Robot via Cmake-commits
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 c831e409a53a33c3b3bdbaa9c19be5ae3364e1f6 (commit) via

Re: [cmake-developers] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

2019-11-05 Thread Alexander
Well, I have tested this proposal as well and I can confirm that it does not work for me. I have added this code to my CMakeLists.txt: string(APPEND CMAKE_SHARED_LINKER_FLAGS " -DEF:\"foo_1.def\" -DEF111:\"foo_1.def\"") string(APPEND CMAKE_CXX_STANDARD_LIBRARIES " -DEF:\"foo_2.def\"") # just in

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-217-gabb0119350

2019-11-05 Thread Kitware Robot via Cmake-commits
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 abb011935013f11048b1fe47b7496ba89c906984 (commit) via