[CMake] Build tool mode with MSBuild not ignoring targets excluded from default

2017-05-04 Thread Kim Kryger
Hello all, I am using the Build Tool Mode in CMake 3.7.1 to build INSTALL targets in a MSVC11 build folder. According to the documentation (and the output from MSBuild), it should be building 'default targets' only, but it doesn't specify what that means exactly. The command I am running: cmake.ex

Re: [CMake] CPack not detecting pkgbuild or product build

2017-05-04 Thread Ayla Khan
OK, good to know. Best, Ayla > On May 4, 2017, at 6:09 AM, Robert Maynard wrote: > > Hi, > > By default the NSIS generator is enabled. > > On Wed, May 3, 2017 at 6:39 PM, Ayla Khan > wrote: > That worked - thank you! Do I need to add NSIS manually for Windows > i

[CMake] avoiding finding system libraries (motivation is superbuilds)

2017-05-04 Thread Kris Thielemans
Hi Short question: if we have a library/include files installed both in the usual system locations and outside, how do we force CMake to find the latter? (without modifying the CMake files of the project). Motivation: We're trying to make a SuperBuild that builds/downloads a specific versi

[CMake] Inconsistent parsing of bracket comments in command arguments

2017-05-04 Thread Volo Zyko
Hi, I've encountered the following behavior. Code like 'set(FOO#[[bar]] 1)' is parsed fine by cmake, but for the code 'set(FOO #[[bar]]1)' cmake reports: Syntax Error in cmake code at column 13 Argument not separated from preceding token by whitespace. Is this by design or just an omission?

Re: [CMake] How to get list of target dependencies?

2017-05-04 Thread Robert Dailey
Forgot to mention, I'm using CMake 3.8.1 On Thu, May 4, 2017 at 10:47 AM, Robert Dailey wrote: > How can I get a list of target dependencies of a target? For example, > if I have 3 library targets that depend on each other like this: > > A -> B -> C > > When I ask for the target dependencies for

[CMake] How to get list of target dependencies?

2017-05-04 Thread Robert Dailey
How can I get a list of target dependencies of a target? For example, if I have 3 library targets that depend on each other like this: A -> B -> C When I ask for the target dependencies for A, I should get a list back with B in it. Basically this would be the same list I pass to target_link_libra

[CMake] What is ANDROID_JAVA_SOURCE_DIR for?

2017-05-04 Thread Robert Dailey
I am seeing hints of ANT / JAVA support for Android in 3.8.1 documentation. Essentially there is a whole list of properties that have unexplained use cases under Properties for Targets. I see ANDROID_JAVA_SOURCE_DIR, for example. What are these for? Will CMake actually do the "ant release" command

Re: [CMake] CPack not detecting pkgbuild or product build

2017-05-04 Thread Robert Maynard
Hi, By default the NSIS generator is enabled. On Wed, May 3, 2017 at 6:39 PM, Ayla Khan wrote: > That worked - thank you! Do I need to add NSIS manually for Windows > installers as well? It looks like CMake finds NSIS without any difficulty > but I’d rather be sure. > > Thanks, > > Ayla > > On

[CMake] When Ninja byproduct is a directory causes `clean` target to fail.

2017-05-04 Thread Dan Liew
Hi, I recently added support to a project to build its API documentation [1]. The documentation is generated by doxygen. I used `add_custom_command()` to run doxygen and I use `BYPRODUCTS` to specify the output directory that will be generated by doxygen in the hope that this would tell ninja to

[CMake] Circular dependencies with Ninja, not with Unix Makefiles

2017-05-04 Thread Ignacio Fernández Galván via CMake
Hello, I have a project where circular dependencies are generated when I use the Ninja generator, but not the default Unix Makefiles. I could create a minimal test like this: $ cat CMakeLists.txt add_subdirectory (ext ${PROJECT_BINARY_DIR}/ext) $ cat ext/CMakeLists.txt set (OUT ${CMAKE_CURRE

Re: [CMake] DLL handling under CMake

2017-05-04 Thread lectem
I managed to get it working by using an intermediate script. One might want to generate the script instead of using the « RUN_IT » variable trick. This was only tested on Windows, but seems to work fine. Put the following code in a xx.cmake file, include it from your CMakeLists.txt and enjoy.