[Cmake-commits] CMake branch, master, updated. v3.6.1-617-g272a2bf

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

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

On Fri, Aug 12, 2016 at 4:58 PM, Roger Leigh wrote: > You can simplify this to two steps: > > 1. Clone the superbuild repository > 2. Build the third-party and first-party packages > > This is the approach we take with the OME super-build >

[CMake] FAQ broken link, "Why does CMake generate recursive Makefiles?"

I don't have access to fix this myself, so I hope someone on this list can. Sorry, I'm not ready to commit to a git membership to report bugs, and hope I'm not butting in where I don't belong. *See FAQ topic link*: https://cmake.org/Wiki/CMake_FAQ#Why_does_CMake_generate_ recursive_Makefiles.3F

[CMake] Empty libraries?

I noticed it is possible to create empty libraries like this: add_library(header-only "header.hpp") set_property(TARGET header-only PROPERTY LINKER_LANGUAGE CXX) On my machine, MinGW spits out an empty 8-byte libheader-only.a, and Visual Studio works too but outputs nothing. Is this even

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

OpenSSL depends on system libraries. When linking statically again OpenSSL, the client target must also link those libraries. This patch updates FindOpenSSL.cmake to include the necessary system libs in the OpenSSL libraries variables and in the OpenSSL::Crypto and OpenSSL::SSL target

[CMake] Exporting files that are not targets

Hello, I am currently working on a project that exports a static library target including its dependencies so that it can be used with the `find_package()' command. With include files this is quite easy by using the $ and the $ generator expressions in combination with the `installl()' command.