Re: [CMake] Any portable way in CMake build tree to find Source tree path?

2013-01-25 Thread Cory Quammen
Kent, I have a CMake function that may be of interest to you (see attached file). For your purposes, use it as follows: GetCMakeCacheValue( "${ABC_BUILD_DIR}" ABC_SOURCE_DIR ) where the project against which you want to build is named "ABC". The first argument must always be the build director

Re: [CMake] Any portable way in CMake build tree to find Source tree path?

2013-01-25 Thread Jean-Christophe Fillion-Robin
Hi Kent, On all the platform, the build tree contains a CMakeCache.txt that will systematically contain the following text: FOO_SOURCE_DIR:STATIC=/path/to/foosource where FOO is the name of the project. You could simply check for the existence of "CMakeCache.txt", and extact the value usin

[CMake] Any portable way in CMake build tree to find Source tree path?

2013-01-25 Thread Kent Williams
I'm trying to write a Find.cmake file for a library that doesn't generate a proper Config.cmake file. The problem I'm trying to solve is how to build against a build tree instead of an install tree. On OS X and Windows (well, probably any Makefile generator) CMake helpfully adds CMakeDirectoryInf

[CMake] Does INSTALL_RPATH work on OS X?

2013-01-25 Thread Matthew LeRoy
Hi, I'm trying to convince CMake to do my bidding with regard to setting the RPATH on one of my executables, and it doesn't seem to be working as I think it should be (according to my understanding of the documentation). I'm running CMake 2.8.10.2 on OS X 10.8.2, and using the Xcode generator. Wh

Re: [CMake] Backslashes in path names on Windows?

2013-01-25 Thread Sascha Cunz
Am Freitag, 25. Januar 2013, 12:52:07 schrieb Kent Williams: > I am testing a ITK patch I'm working on in Windows. That involves entering > a path in cmake-gui or ccmake. The first time I tried it, I entered the > path 'windows-wise' with backslashes as path separators. > > That caused a syntax

[CMake] Backslashes in path names on Windows?

2013-01-25 Thread Kent Williams
I am testing a ITK patch I'm working on in Windows. That involves entering a path in cmake-gui or ccmake. The first time I tried it, I entered the path 'windows-wise' with backslashes as path separators. That caused a syntax error at the point where that variable is used. When I re-entered the

Re: [CMake] find_packge behavior regarding enabled languages

2013-01-25 Thread xantares 09
>From: e...@sf-mail.de >To: cmake@cmake.org >Date: Fri, 25 Jan 2013 19:00:56 +0100 >Subject: Re: [CMake] find_packge behavior regarding enabled languages >xantares 09 wrote: > >From: xantare...@hotmail.com > >To: cmake@cmake.org > >Date: Thu, 24 Jan 2013 08:12:49 + > >Subject: [CMake]

Re: [CMake] find_packge behavior regarding enabled languages

2013-01-25 Thread Rolf Eike Beer
xantares 09 wrote: > >From: xantare...@hotmail.com > >To: cmake@cmake.org > >Date: Thu, 24 Jan 2013 08:12:49 + > >Subject: [CMake] find_packge behavior regarding enabled languages > >I noticed that when all languages are disabled through the project command: > >project ( Foo NONE ) > > > >...

Re: [CMake] find_packge behavior regarding enabled languages

2013-01-25 Thread xantares 09
>From: xantare...@hotmail.com >To: cmake@cmake.org >Date: Thu, 24 Jan 2013 08:12:49 + >Subject: [CMake] find_packge behavior regarding enabled languages > >Hi, > >I noticed that when all languages are disabled through the project command: >project ( Foo NONE ) > >... then a dependent Bar