[CMake] How are modules tested?

I've been having difficulties creating an Xcode project. In the course of this work, I've had occasion to investigate the FindBoost.cmake file. Looking at it - I don't see how it can possible work. On my system libraries are created libboost___abi.a and I don't see anything similar to this.

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-434-gffe7896

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

[CMake] CPACK WIX shortcuts

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 feature), then I tried to build the unit test and I

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

One usage I would have had for this feature would have been to generate a pre-linked library. Basically, merging a static library and its dependencies together (check ld -r) and output an object file for static linking (not a shared library). This is required as merging static libraries may

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

We are trying to develop a proper C++ dependency management tool which will combine Ivy together with CMake. Our intention is to open source this this modules later for everyone. As we need to keep track of all dependencies we would like to be able to get all transitive linked libraries to be

Re: [CMake] Building CMake without Curl

Hi Jayesh, CMake includes internal versions of all the dependencies it needs to build. You have the option of using an external system-supplied version but it's certainly not required. Without OpenSSL you'll just have a cmake that can't use https, certainly not the end of the world. The

Re: [cmake-developers] Add CXX_STANDARD support for Intel C++ compilers

On 11/02/2016 03:32 PM, Levi Morrison wrote: > Brad, here it is a year later and thought I would get around to > finishing this work. Then I discovered you had already completed it! > Thank you so much! > > I now have access to the 2017 Intel C++ compiler; is there anything in > particular you'd

Re: [cmake-developers] Add CXX_STANDARD support for Intel C++ compilers

On Wed, Dec 2, 2015 at 8:40 AM, Brad King wrote: > On 12/02/2015 10:31 AM, Levi Morrison wrote: >> Hmm. What is the purpose of this module? I verified that indeed my >> changeset somehow breaks this test but I don't even understand what it >> is trying to do. At a glance it

Re: [CMake] Building CMake without Curl

Jayesh, Use Spack. Spack has no problem auto-building CMake for you, along with curl and whatever else it needs. https://github.com/llnl/spack/ -- Elizabeth On Wed, Nov 2, 2016 at 1:08 PM, Jayesh Badwaik wrote: > Hi, > > Is there a way to build CMake without curl?

[CMake] Building CMake without Curl

Hi, Is there a way to build CMake without curl? I am currently in an environment where I have no openssl-dev packages nor libcurl-dev packages. So, if I want to build CMake, I will need to build openssl-dev myself which I do not want to do. I can ask my sysadmin for the packages, but I was

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-910-gd44f192

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-902-g39ec090

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-900-g77b88ee

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-898-g612bb57

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-896-g88ee873

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-433-gab2ae48

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

[Cmake-commits] CMake branch, release, updated. v3.7.0-rc2-34-gc555eca

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-891-gbc58351

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-889-g619df3f

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-429-g316206e

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-885-gcd060d3

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-426-gcea2678

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-424-gb5ad094

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-882-gc7d27ed

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-880-g66b673c

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-877-g3b3b596

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-421-gf6b93fb

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-419-g6a65f05

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc2-416-g93f0251

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-872-g7cb0f78

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

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

On 11/01/2016 04:30 PM, maikel van den Hurk wrote: > obtain actually all transitive linked libraries of a specific target. [snip] > this information is only fully available during generation time. What is an example use case for this? I don't think we can offer a configure-time solution but