Re: [CMake] dependencies between external projects (not DEPENDS)

Usually there would be variables like A_ROOT which allow the FindA.cmake module being used by B to correctly find everything. If there isn't, you'd have to write your own FindA.cmake module in either case. If you can't modify B, you could use the patch step of the external project to replace the

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 17-Aug-16 04:29, Florent Castelli wrote: The Boost source download is cached outside of the build directory in a unique folder. So it’s effectively only done once for all platforms and then reused. This is true for local machines and for custom build servers like your personal Jenkins.

Re: [CMake] Private dependencies of static libraries exported as targets

On 2016-08-17 at 05:19 -0500, Nicholas Braden wrote: > Huh, this is weird. It seems to be an issue with the export/import > mechanism. If you make a project where everything is in the same > CMakeLists.txt and there is no install step, there is no include > directory pollution. See my attached

Re: [CMake] Private dependencies of static libraries exported as targets

On 2016-08-16 at 20:14 -0500, Nicholas Braden wrote: > Ah, I misunderstood what you were asking about. It would be pretty > weird if CMake didn't know that static libraries always need all > their > dependencies linked regardless of privacy, but I agree it should at > least be mentioned somewhere.

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

On 17-Aug-16 08:36, Elizabeth A. Fischer wrote: > > I don't think CMake is the best place to do it, > Can you provide any details? I personally think that CMake is a > natural and the only place where it should be done. The most important reason here is because there are combinatorially many

[CMake] Example of using Visual Studio for Nightly Dashboard

Can anyone point my to a project, including scripts etc, that shows how to use Visual Studio as the build mechanism for a Visual Fortran project? My Problem is the following: I am generating a Visual Studio with Intel Fortran compiler (v16.x) from CMake but when I load the resulting sln file

[Cmake-commits] CMake branch, next, updated. v3.6.1-1282-g644cdf7

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

Re: [cmake-developers] FindOpenSSL: Link libraries needed for static OpenSSL.

Am 2016-08-17 14:53, schrieb Brad King: On 08/16/2016 04:44 PM, Alexander Lamaison wrote: I've attached a new patch without the changes to the singular-named variables. Thanks. +if(WIN32 AND NOT CYGWIN) + set_target_properties(OpenSSL::Crypto PROPERTIES +

Re: [cmake-developers] FindOpenSSL: Link libraries needed for static OpenSSL.

On 08/16/2016 04:44 PM, Alexander Lamaison wrote: > I've attached a new patch without the changes to the singular-named variables. Thanks. > +if(WIN32 AND NOT CYGWIN) > + set_target_properties(OpenSSL::Crypto PROPERTIES > +INTERFACE_LINK_LIBRARIES crypt32) > +else() > +

[Cmake-commits] CMake branch, next, updated. v3.6.1-1280-g2b71053

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

Re: [cmake-developers] [PATCH v7] For Windows encode process output to internally used encoding

On 08/17/2016 06:11 AM, Dāvis Mosāns wrote: >> Applied with minor tweaks and merged to `next` for testing: > > Great! Thanks! I squashed in one warning fix: Windows: Encode child process output to internally-used encoding https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=12924660 However,

[Cmake-commits] CMake branch, next, updated. v3.6.1-1284-gc541113

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1291-g253e20a

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1294-g15df44b

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-643-g5d16907

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-640-g76ff725

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-649-g67a7dce

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-645-gc700d11

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-647-g29593b7

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1297-g2e928b1

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

[cmake-developers] [PATCH] Tests: Refactor testing of extra generators.

From: Chaoren Lin Use a loop instead of repeating the same thing multiple times. --- Tests/CMakeLists.txt | 77 1 file changed, 30 insertions(+), 47 deletions(-) diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt

[Cmake-commits] CMake branch, next, updated. v3.6.1-1300-g951bc07

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1302-g1cca31b

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-650-g11e0cea

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