Re: [CMake] Changed behavior of CPACK_PACKAGE_VERSION generation?

2019-05-26 Thread Craig Scott
A little late, but finally got a chance to look at this. In CMake 3.12.0, the CPack version handling in Modules/CPack.cmake was changed to take its default from the project version, if set. This was implemented but the following logic: if(CMAKE_PROJECT_VERSION_PATCH) ... endif() This intro

[CMake] Questin about ExternalProject_Add

2019-05-26 Thread Steven Truppe
Hi everyone, i'm trying to create a build system that download all needed libraries with ExternalProject_Add. i've the following lines in my CMakeLists.txt: option(WITH_LIB_GLFW "Support for the GLFW library. (default: 1)" 1) option(WITH_LIB_NLOHMANN_JSON "Support for the nlohmann JSON library.

Re: [CMake] Problems with ExternalProject_Add

2019-05-26 Thread Craig Scott
On Wed, May 22, 2019 at 7:13 PM Steven Truppe wrote: > Hi everyone, > > > i'm trying to use ExternalProject_Add like the following: > > set(BOOST_VERSION 1.68.0) > set(BOOST_VERSION_NODOTS 1_68_0) > set(BOOST_URI > https://dl.bintray.com/boostorg/release/${BOOST_VERSION}/source/boost_${BOOST_VER