Re: [CMake] Link Error with OS X 10.5, using 104u SDK, CMake 2.6.0

2008-07-25 Thread Mike Jackson
I really need to search the file archives first.. http://www.cmake.org/pipermail/cmake/2008-January/019464.html Sorry for the noise Is it worth putting something in my cmake code to detect the condition where I am on 10.5 but using the 10.4u sdk and then export the environment variable:

[CMake] CMake CVS + CPack + NSIS - Installing files with spaces

2008-07-25 Thread Gregory Peele ARA/CFD
I'm really pleased with the component-based CPack installer with the NSIS backend, and am currently using the July 24th CVS snapshot of CMake to take advantage of it. Today I ran into a puzzler though. Some of the files I'm installing have spaces in the relative path, and the NSIS script

[CMake] CTEST_ENVIRONMENT in non-declarative script

2008-07-25 Thread Milan Dorak
Hey guyz, i have been using declarative ctest script and command SET (CTEST_ENVIRONMENT LC_ALL=C ) This isn't working in new non-declarative scripts. Sure I can do export LC_ALL=C, but i would rather have it in script like before. Any suggestions ? Thanks

[CMake] re-running cmake with different flags doesn't work

2008-07-25 Thread Andreas Pakulat
Hi, I've just noticed that re-running cmake and changing -DCMAKE_CXX_FLAGS doesn't work as one would expect. This claims to be rebuilding the makefiles, however after running a make clean and make VERBOSE=1 I don't see the flags being applied. To make this clear, what I'm doing is: cmake ../

Re: [CMake] Feature wish - constrained string values for configuration options

2008-07-25 Thread Robert Haines
On 24 Jul 2008, at 23:17, Alexander Neundorf wrote: On Thursday 24 July 2008, Robert Haines wrote: On 18 Jul 2008, at 18:40, Bill Hoffman wrote: ... However, it is not that easy to implement, since the basic type in CMake is a string. There is no way to constrain the value of a variable,

[CMake] Recursive custom target

2008-07-25 Thread Boris Boesler
This seems to be a FAQ (http://www.cmake.org/pipermail/cmake/2003-May/003799.html ) but I can't find a proper solution for cmake 2.6-patch 0. In cmake 2.4 I used ADD_CUSTOM_TARGET() in each CMakeLists.txt file in every subdirectory where this target should exist - no problem so far. In

Re: [CMake] re-running cmake with different flags doesn't work

2008-07-25 Thread Werner Smekal
Hi, if you change cmake settings it's always best to delete the build folder. So in your case: cmake ../ make rm -rf ../build/* cmake -DCMAKE_CXX_FLAGS=-g ../ make VERBOSE=1 should bring the desired results. Werner On 25.07.2008, at 10:29, Andreas Pakulat wrote: Hi, I've just noticed

Re: [CMake] CTEST_ENVIRONMENT in non-declarative script

2008-07-25 Thread David Cole
SET(ENV{LC_ALL} C) On Fri, Jul 25, 2008 at 4:24 AM, Milan Dorak [EMAIL PROTECTED] wrote: Hey guyz, i have been using declarative ctest script and command SET (CTEST_ENVIRONMENT LC_ALL=C ) This isn't working in new non-declarative scripts. Sure I can do export LC_ALL=C, but i would rather

Re: [CMake] re-running cmake with different flags doesn't work

2008-07-25 Thread Andreas Pakulat
On 25.07.08 13:02:06, Werner Smekal wrote: Hi, if you change cmake settings it's always best to delete the build folder. So in your case: cmake ../ make rm -rf ../build/* cmake -DCMAKE_CXX_FLAGS=-g ../ make VERBOSE=1 should bring the desired results. Of course, but thats not really

Re: [CMake] Feature wish - constrained string values for configuration options

2008-07-25 Thread Andreas Pokorny
Hello, From my point of view as a user, it would be sufficient if the cmake (G)UIs would support it as a kind of combobox. Additionally to that cmake or a macro could do the validation during the generation step. I only had that need for a little GUI thing. Our software can be configured in many

Re: [CMake] CTEST_ENVIRONMENT in non-declarative script

2008-07-25 Thread Bill Hoffman
Milan Dorak wrote: Hey guyz, i have been using declarative ctest script and command SET (CTEST_ENVIRONMENT LC_ALL=C ) This isn't working in new non-declarative scripts. Sure I can do export LC_ALL=C, but i would rather have it in script like before. Any suggestions ? Thanks set(ENV{LC_ALL}

[CMake] 2.6.1 RC12 add_subdirectory(xxx EXCLUDE_FROM_ALL) problems

2008-07-25 Thread Ross, Thomas
Hello List! I was planning to switch a project from CMake 2.4.8 to CMake 2.6.1 when it hits final and was trying out the newest RC12 to see if it works for me so far. So what am I doing... I have an add_subdirectory(3rdParty EXCLUDE_FROM_ALL) in my main CMakeLists.txt that generates a

Re: [CMake] re-running cmake with different flags doesn't work

2008-07-25 Thread Brad King
Andreas Pakulat wrote: Hi, I've just noticed that re-running cmake and changing -DCMAKE_CXX_FLAGS doesn't work as one would expect. This claims to be rebuilding the makefiles, however after running a make clean and make VERBOSE=1 I don't see the flags being applied. To make this clear,

Re: [CMake] re-running cmake with different flags doesn't work

2008-07-25 Thread Andreas Pakulat
On 25.07.08 11:56:17, Brad King wrote: Andreas Pakulat wrote: I've just noticed that re-running cmake and changing -DCMAKE_CXX_FLAGS doesn't work as one would expect. This claims to be rebuilding the makefiles, however after running a make clean and make VERBOSE=1 I don't see the flags

Re: [CMake] 2.6.1 RC12 add_subdirectory(xxx EXCLUDE_FROM_ALL) problems

2008-07-25 Thread Bill Hoffman
Ross, Thomas wrote: Hello List! I was planning to switch a project from CMake 2.4.8 to CMake 2.6.1 when it hits final and was trying out the newest RC12 to see if it works for me so far. So what am I doing... I have an add_subdirectory(3rdParty EXCLUDE_FROM_ALL) in my main CMakeLists.txt that

[CMake] Link Error with OS X 10.5, using 104u SDK, CMake 2.6.0

2008-07-25 Thread Mike Jackson
I am getting the following link error when trying to link one of my projects. ld: library not found for -ldylib1.10.5.o collect2: ld returned 1 exit status make[2]: *** [Bin/libtiff_debug.dylib] Error 1 make[1]: *** [CMakeFiles/tiff.dir/all] Error 2 make: *** [all] Error 2 The complete link