[CMake] CMAKE_OSX_SYSROOT being ignored with frameworks in /Library/Frameworks

2014-04-23 Thread James Bigler
I have CMAKE_OSX_SYSROOT defined as something: set(CMAKE_OSX_SYSROOT "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk" CACHE LIST "OSX sysroot SDK directory" FORCE) Then later I do a find_library command and it finds a library framework in /Libra

[CMake] OSX Bundles and wrapper scripts

2014-04-23 Thread Zaak Beekman
If I want to create an OSX bundle, but I want the main executable to be a configured wrapper script written in bash, what is the best way to go about doing that? It seems that the Also, how do I get the wrapper script to correctly call the compiled executable so that the app bundle is relocatable?

[CMake] Are the [Project name]_SOURCE_DIR variables stored in the cache ?

2014-04-23 Thread Glenn Coombs
I'm using cmake version 2.8.12.1 and have just encountered an issue with my cmake setup where I was using the [Project name]_SOURCE_DIR variable in an include_directories command and it was being ignored. In my top level CMakeLists.txt I had: project(blah) add_subdirectory(foo) add_subdirectory(

[CMake] target_include_directories and relative paths inside generator expressions.

2014-04-23 Thread Andrew Fuller
Running CMake 3.0-rc3 and the docs for target_include_directories say the paths may be absolute or relative. Indeed the following works as desired: target_include_directories( MyTarget PRIVATE some/dir ) The docs also mention that generator expressions can be used. However the following produce

Re: [CMake] --find-package option fails with some of the Qt5 components

2014-04-23 Thread Alan W. Irwin
On 2014-04-23 14:30+0200 Stephen Kelly wrote: Alan W. Irwin wrote: Hi Steve: PLplot not only CMake exports its libraries but also provides library information in pkg-config form for our users that prefer that form. Therefore, for this component of our install I need to collect explicit compil

Re: [CMake] Explanation....

2014-04-23 Thread Matthew Woehlke
On 2014-04-16 06:03, Rolf Eike Beer wrote: Am 16.04.2014 11:39, schrieb Johannes Zarl: Instead of ``"${var}" STREQUAL "VALUE"'', write: IF ( var MATCHES "^VALUE$" ) NO, please don't! I try hard to kill all those as it requires compiling a regular expression for a simple string match. Just

Re: [CMake] good way to append link flags?

2014-04-23 Thread Nils Gladitz
On 23.04.2014 18:16, Clinton Stimpson wrote: I am using set_property(TARGET mytarget APPEND PROPERTY LINK_FLAGS "...") multiple times to add various link flags. But when I inspect the actual link command, I see all my flags separated by semi-colons and no spaces between them, which is not what I

Re: [CMake] good way to append link flags?

2014-04-23 Thread Clinton Stimpson
On Wednesday, April 23, 2014 06:25:24 PM Nils Gladitz wrote: > On 23.04.2014 18:16, Clinton Stimpson wrote: > > I am using > > set_property(TARGET mytarget APPEND PROPERTY LINK_FLAGS "...") > > multiple times to add various link flags. > > > > But when I inspect the actual link command, I see all

[CMake] good way to append link flags?

2014-04-23 Thread Clinton Stimpson
I am using set_property(TARGET mytarget APPEND PROPERTY LINK_FLAGS "...") multiple times to add various link flags. But when I inspect the actual link command, I see all my flags separated by semi-colons and no spaces between them, which is not what I want. Is this correct behavior for cmake?

Re: [CMake] --find-package option fails with some of the Qt5 components

2014-04-23 Thread Stephen Kelly
Alan W. Irwin wrote: > Hi Steve: > > PLplot not only CMake exports its libraries but also provides library > information in pkg-config form for our users that prefer that form. > Therefore, for this component of our install I need to collect > explicit compile and link flags for Qt5, and it appea

Re: [CMake] CDash questions

2014-04-23 Thread David Cole
> The way I’m doing this now is the following: > > a) I edit the CMakeList.txt file(s) and follow > the procedure to create an Xcode IDE project. > This project contains a bunch of targets > including ALL_BUILD, RUN_TESTS, and > Experimental - among others You should not hav