Re: [CMake] source_group with XCode?

Post a bug to the bug tracker. Maybe someone will get to it. -- Mike Jackson On Dec 11, 2009, at 5:26 PM, Glenn Hughes wrote: Xcode definitely supports it. I'm moving to CMake from a pure Xcode project, and we have some deeply nested folders. My guess is its a bug in the generator. I'm running

Re: [CMake] source_group with XCode?

I just tested the same project with Visual Studio 2008 and CMake 2.6.4 and in the generated solution file I do get the correct number of sub folders generated. I would say that there may be a bug with the XCode generator or XCode may not support the feature ?!? -- Mike Jackson On Dec 11, 2

Re: [CMake] source_group with XCode?

Ya, know you are right. I have another project that should have something like: MXA/Common/IO/Private and I get "Common" and "Private" as subgroups of MXA, instead of a nice hierarchy. You may have found a bug. I am running CMake 2.6.4. Don't have 2.8 yet. --- Mike Jackson

Re: [CMake] FindOpenCV.cmake

On Fri, Dec 11, 2009 at 03:38:01PM -0500, David Doria wrote: > What is the process for getting a library added to cmake? > > The instructions for installing OpenCV have the user download > FindOpenCV.cmake and put it in their cmake/modules directory > http://opencv.willowgarage.com/wiki/Getting_st

Re: [CMake] Eclipse tries to build x64 instead of x86

> Ok, nevermind, I built again using "-DCMAKE_BUILD_TYPE=Release" and that > worked.  I wiped the build directory entirely and did > "-DCMAKE_BUILD_TYPE=Release" and it's working again.  Strange.  Maybe some > files just got screwed up somehow.  That seems to have fixed it so please > disregard

Re: [CMake] Eclipse tries to build x64 instead of x86

Ok, nevermind, I built again using "-DCMAKE_BUILD_TYPE=Release" and that worked. I wiped the build directory entirely and did "-DCMAKE_BUILD_TYPE=Release" and it's working again. Strange. Maybe some files just got screwed up somehow. That seems to have fixed it so please disregard my prev

Re: [CMake] source_group with XCode?

source_group( NameSubName FILES ${source} ) _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Dec 11, 2009,

Re: [CMake] Embedding up-to-date version info in built library

On 11. Dec, 2009, at 16:58 , Kolja Waschk wrote: > Hi, thanks, > >> One question: Why do you need a add_custom_command with all those >> dependencies? Why does version.cc depend on all the source and header >> files? What do you write in your version.cc file? Is it something like > > Beside the

[CMake] source_group with XCode?

Hi again, I'm trying to use the source_group command with XCode, and its marginally working, but in a flaky sorta way. I was wondering what other people have any tips. The behavior I'm seeing is: Groups in the form source_group( Name FILES ${source} ) Work OK, they ad

[CMake] Eclipse tries to build x64 instead of x86

I'm trying the Eclipse generator for the first time since loading 2.8. When I generate using "NMake Makefiles", I can run "nmake" and everything builds correctly using x86. When I use generator "Eclipse CDT4 - NMake Makefiles", I get an environment I can successfully import into eclipse. When

[CMake] FindOpenCV.cmake

What is the process for getting a library added to cmake? The instructions for installing OpenCV have the user download FindOpenCV.cmake and put it in their cmake/modules directory http://opencv.willowgarage.com/wiki/Getting_started?action=AttachFile&do=view&target=FindOpenCV.cmake Can this be in

Re: [CMake] Building tests only for "make test"

Hi Stefan, I once dug into this issue, because I wanted to (more or less) emulate the GNU Autotools 'make check' feature. Have a look at http://www.cmake.org/Wiki/CMakeEmulateMakeCheck and see if that answers you question. Best regards, Marcel Loose. On Fri, 2009-12-11 at 15:53 +0100, Dr. Stefan

Re: [CMake] Embedding up-to-date version info in built library

Hi, thanks, One question: Why do you need a add_custom_command with all those dependencies? Why does version.cc depend on all the source and header files? What do you write in your version.cc file? Is it something like Beside the SVN revision number of the working base, our embedded revision i

Re: [CMake] Embedding up-to-date version info in built library

On 11. Dec, 2009, at 15:53 , Kolja Waschk wrote: > Hi, > > I know that similar questions have been posted before, but as far as I > have been able to follow, no real solution was ever given. > > The goal is to embed revision information in a C++ library "mylib". > > I already managed to use "c

Re: [CMake] Embedding up-to-date version info in built library

the list of sources. But another problem came up: Only the first single list item seems to be scanned for implicit dependencies. And I failed to come up with a list or command syntax that would allow me to have the other 99+ sources scanned as well. I think I came up with a usable workaround for

[CMake] Use a custom linker

Hi, I want to crosscompile a project. I created a toolchain file. But I've problems because the linking step use the compiler to link. My need to uses another tool to link. How can I force cmake to use a different linker? I've posted also on stackoverflow: http://stackoverflow.com/questions/1

[CMake] Embedding up-to-date version info in built library

Hi, I know that similar questions have been posted before, but as far as I have been able to follow, no real solution was ever given. The goal is to embed revision information in a C++ library "mylib". I already managed to use "create_custom_target" so that an external program is executed to cr

[CMake] Building tests only for "make test"

Hi all, I face a (probably simple) problem: I want to build a project, that includes tests, but these should not be build on default, so I added EXCLUDE_FROM_ALL to the add_executable command. How can I force them to be built when testing ? (we test through make test and continuously

Re: [CMake] Can cmake generate Visual Studio projects without generating a makefile?

You can do what you want with add_custom_command and add_custom_target. Have you read about those CMake commands...? http://cmake.org/cmake/help/cmake-2-8-docs.html#command:add_custom_command http://cmake.org/cmake/help/cmake-2-8-docs.html#command:add_custom_target HTH, David On Fri, Dec 11, 2

Re: [CMake] cmake -E create_symlink for Windows

On 11. Dec, 2009, at 15:35 , Hendrik Sattler wrote: > Zitat von Michael Wild : >> On 11. Dec, 2009, at 15:17 , Hendrik Sattler wrote: >>> Zitat von Michael Wild : On 11. Dec, 2009, at 14:27 , Marcel Loose wrote: > I was browsing the CMake sources for a problem I was facing with the >

Re: [CMake] cmake -E create_symlink for Windows

On Fri, Dec 11, 2009 at 9:18 AM, Marcel Loose wrote: > On Fri, 2009-12-11 at 14:51 +0100, Michael Wild wrote: > > On 11. Dec, 2009, at 14:27 , Marcel Loose wrote: > > > > > Hi all, > > > > > > I was browsing the CMake sources for a problem I was facing with the > > > creation of symlinks (on Unix

Re: [CMake] cmake -E create_symlink for Windows

Zitat von Michael Wild : On 11. Dec, 2009, at 15:17 , Hendrik Sattler wrote: Zitat von Michael Wild : On 11. Dec, 2009, at 14:27 , Marcel Loose wrote: I was browsing the CMake sources for a problem I was facing with the creation of symlinks (on Unix that is) and I noticed that the SystemTools:

Re: [CMake] cmake -E create_symlink for Windows

Zitat von Michael Wild : On 11. Dec, 2009, at 14:27 , Marcel Loose wrote: I was browsing the CMake sources for a problem I was facing with the creation of symlinks (on Unix that is) and I noticed that the SystemTools::CreateSymlink function simply returns false when building on a Windows platfor

Re: [CMake] CPack & WiX

Tim St. Clair wrote: I was just wondering if anyone has created a WiX cpack-generator yet, the wiki says "no", but the wiki is stale and I'm rather surprised that no one has done it. No, still not done. -Bill ___ Powered by www.kitware.com Visit ot

Re: [CMake] cmake -E create_symlink for Windows

On Fri, 2009-12-11 at 14:51 +0100, Michael Wild wrote: > On 11. Dec, 2009, at 14:27 , Marcel Loose wrote: > > > Hi all, > > > > I was browsing the CMake sources for a problem I was facing with the > > creation of symlinks (on Unix that is) and I noticed that the > > SystemTools::CreateSymlink fun

[CMake] Can cmake generate Visual Studio projects without generating a makefile?

If I have a build system in place (that uses gmake) that I am already comfortable with and would just like to use cmake to create Visual Studio (or XCode) projects that simply have release and debug targets that call gmake for me, can I do that with cmake? Or, does cmake always generate a makefile

Re: [CMake] cmake -E create_symlink for Windows

On 11. Dec, 2009, at 14:27 , Marcel Loose wrote: > Hi all, > > I was browsing the CMake sources for a problem I was facing with the > creation of symlinks (on Unix that is) and I noticed that the > SystemTools::CreateSymlink function simply returns false when building > on a Windows platform. >

[CMake] CPack & WiX

I was just wondering if anyone has created a WiX cpack-generator yet, the wiki says "no", but the wiki is stale and I'm rather surprised that no one has done it. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-sourc

[CMake] cmake -E create_symlink for Windows

Hi all, I was browsing the CMake sources for a problem I was facing with the creation of symlinks (on Unix that is) and I noticed that the SystemTools::CreateSymlink function simply returns false when building on a Windows platform. Does that mean that I cannot use 'cmake -E create_symlink' on W

Re: [CMake] CTest ignoring custom set variables

David Cole wrote: > On Fri, Dec 11, 2009 at 3:58 AM, Martin Apel > wrote: > > Hi all, > > I tried to set some CTest custom variables such as > CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE in the CTestCustom.cmake > file in the binary directory. >

Re: [CMake] CTest ignoring custom set variables

On Fri, Dec 11, 2009 at 3:58 AM, Martin Apel wrote: > Hi all, > > I tried to set some CTest custom variables such as > CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE in the CTestCustom.cmake > file in the binary directory. > This works as long as I run ctest interactively, e.g. "ctest -D > Experime

Re: [CMake] Is it safe to add properties to custom target?

On Fri, Dec 11, 2009 at 3:55 AM, Marcel Loose wrote: > On Thu, 2009-12-10 at 22:24 +0100, Alexander Neundorf wrote: > > On Wednesday 09 December 2009, Marcel Loose wrote: > > > Hi all, > > > > > > In fact the subject title says it all. Is it safe to do, for example: > > > > > > add_custom_target(

Re: [CMake] ctest-2.6.4 and ctest 2.8.0 - LIST(FIND ...) always returns -1

Hi again, ok, I did not realize that the LIST functions take the variable name instead of the list content as argument (that is not documented anywhere). However, after trying all possible variants I got it to work now using SET(MYLIST foo bar) SET(ITEM2FIND foo) LIST(FIND MYLIST ${ITEM2FIND}

Re: [CMake] ctest-2.6.4 and ctest 2.8.0 - LIST(FIND ...) always returns -1

Sorry for the typos, I tested it with 2.6.4 and 2.8.0; The return value is (separated by ; not ,) "Index of "foo" in list "foo;bar" is -1" Regards Am 11.12.2009 12:06, schrieb Clemens Arth: > Hi, > > probably I did something wrong, but with both ctest 2.6.4 and 2.8.0 the > following is not

[CMake] ctest-2.6.4 and ctest 2.6.8 - LIST(FIND ...) always returns -1

Hi, probably I did something wrong, but with both ctest 2.6.4 and 2.8.0 the following is not working: SET(MYLIST foo bar) SET(ITEM2FIND foo) LIST(FIND "${MYLIST}" "${ITEM2FIND}" INDEX) MESSAGE(FATAL_ERROR "Index of \"${ITEM2FIND}\" in list \"${MYLIST}\" is ${INDEX}") always returns "Inde

[CMake] CTest ignoring custom set variables

Hi all, I tried to set some CTest custom variables such as CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE in the CTestCustom.cmake file in the binary directory. This works as long as I run ctest interactively, e.g. "ctest -D Experimental". In this case, the test output is not cut off. If I do the sa

Re: [CMake] Is it safe to add properties to custom target?

On Thu, 2009-12-10 at 22:24 +0100, Alexander Neundorf wrote: > On Wednesday 09 December 2009, Marcel Loose wrote: > > Hi all, > > > > In fact the subject title says it all. Is it safe to do, for example: > > > > add_custom_target(myTarget) > > set_target_properties(myTarget PROPERTIES > > LOCATIO