[CMake] Specifying individual install locations at CPack time

Hi, I'm creating a small library (https://github.com/Forty-Bot/appdir) using CMake, and I would like to package it with CPack. I build a shared library, and some html documentation. In addition to that, I need to ship the headers, the README, and the license. If I were to make an archive by hand,

[CMake] Mapping configurations and include_external_msproject()

Hi, I'm using CMake for a project which (on Windows) uses include_external_msproject() to import Visual Studio project files which were generated by another build system. These project files do not contain the usual "Debug" and "Release" configurations, but have a large set of configurations

Re: [CMake] Compiling cmake-3.10.2 against ncursesw

bump -Original Message- From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of John Frankish Sent: Monday, 05 March 2018 15:45 To: cmake@cmake.org Subject: [CMake] Compiling cmake-3.10.2 against ncursesw Hi, I've been trying to compile cmake-3.10.2 on a system that has only ncursesw

Re: [CMake] What are the actual benefits of namespaced targets?

On 2018-03-08 20:05+0100 Nils Gladitz wrote: On 08.03.2018 19:50, Alan W. Irwin wrote: So what are the actual benefits of namespacing the exported targets associated with libraries? On the consumer side it makes linking to targets less error prone. When you link to a library target without

Re: [CMake] CMake misidentifies xlc++ as Clang

Just to roundtrip this for posterity. The fix for incorrect identification of XLC will be in CMake 3.11.0-rc3 On Thu, Mar 8, 2018 at 11:17 AM, Robert Maynard wrote: > Hi. > > 1. You can report this issue on the CMake gitlab ( > https://gitlab.kitware.com/cmake/cmake/issues ). You will want to > a

Re: [CMake] What are the actual benefits of namespaced targets?

On 08.03.2018 19:50, Alan W. Irwin wrote: So what are the actual benefits of namespacing the exported targets associated with libraries? On the consumer side it makes linking to targets less error prone. When you link to a library target without a namespace and e.g. get the name or scope wro

[CMake] What are the actual benefits of namespaced targets?

I am currently trying to update three CMake-based build systems (for PLplot, ephcom, and te_gen) to use best practices following the really useful example of best practice given at . That example uses the NAMESPACE signature f

Re: [CMake] CMake misidentifies xlc++ as Clang

Hi. 1. You can report this issue on the CMake gitlab ( https://gitlab.kitware.com/cmake/cmake/issues ). You will want to attach the result of dumping all defines from the compiler ( xlc++ -dD -E - < /dev/null or xlc++ -dM -E ). Currently it looks like we are using '__IBMCPP__' to detect xlc++, a

[CMake] GoogleTest integration with CTest

​Hi all, I'm a new poster on this list. It's nice to meet you. ​ I ​ was very excited when I came across the new support for GoogleTest test discovery in CMake ( https://blog.kitware.com/dynamic-google-test-discovery-in-cmake-3-10/). However, this new approach and the older one both play very poo

Re: [CMake] GSOC 2018 CMake Project for Kodi

Alright, signing up for a community college course does suffice. I'm definitely interested in this project. My actual computer is going to be down for at least a few more days. The damn thing sprung a leak, and Performance pcs is out of the right tubes. (using mobile for now) I should be back up a