Re: [CMake] Forcing CMake to place targets in directories?

I wanted my vcproj files to be placed in "test_projects". Any idea how I can make this happen? On Thu, Dec 4, 2008 at 8:30 PM, Mike Jackson <[EMAIL PROTECTED]>wrote: > CMAKE_CURRENT_SOURCE_DIR denotes your source tree and NOT the build > tree. Are you building in your source tree instead of using

Re: [CMake] Forcing CMake to place targets in directories?

CMAKE_CURRENT_SOURCE_DIR denotes your source tree and NOT the build tree. Are you building in your source tree instead of using a dedicated build directory? To answer your code you are setting the output directory of where the executable will be placed in a directory called "test_projects" at the

Re: [CMake] How to make ctest not buffer its output?

Alexander Neundorf wrote: On Thursday 04 December 2008, Hugo Heden wrote: Good day all, I use ctest --build-and-test to do some stuff that takes a long time. It seems that ctest buffers the output of its subcommands so that nothing is written (to the "terminal") until at the end. This is a litt

Re: [CMake] 'unset' not in --help-commands-list (also, attn: neundorf)

On Thu, Dec 4, 2008 at 5:36 PM, Matthew Woehlke < [EMAIL PROTECTED]> wrote: > Philip Lowman wrote: > >> On Tue, Nov 18, 2008 at 6:39 PM, Matthew Woehlke wrote: >> >>> Need a bug opened for this or is it trivial enough to fix on the spot? >>> >> >> unset appears to be in --help-commands and --help

[CMake] Forcing CMake to place targets in directories?

Hi, I'm trying to use set_target_properties() to make CMake place generated vcproj files in a subdirectory of ${CMAKE_CURRENT_SOURCE_DIR}. This isn't working and I'm not sure what I'm doing wrong. Below is what I'm doing: set( test_project_name ${project_name}_test_${test_name} )

[CMake] MSVC71 WholeProgramOptimization flags (/LTCG and /GL)

Hi, I would like to reopen issue #0006794 dealing with this linker warning that is still present for MSVC 7.1 static library builds: Linking CXX static library ..\build\MT-DLL\Util-SL.lib XMLWriter.cpp.obj : warning LNK4218: non-native module found; restarting I did some more investiga

Re: [CMake] source_group() and solution directories

> By directories I mean "Solution Folders", sorry for the confusion. > This is a feature that allows you to add "Folders" to the solution. > This has nothing to do with projects. You can add files to these > solution folders. Solution folders are at the same level tree-wise > as projects are (Direc

Re: [CMake] what is wrong with this snippet? (bug?)

Bill Hoffman wrote: Matthew Woehlke wrote: Matthew Woehlke wrote: set(!BANG wacky CACHE STRING "" FORCE) set("var with space" wacky CACHE STRING "" FORCE) message(STATUS "This is !BANG: ${!BANG}") message(STATUS "This is var with space: ${var with space}") The above snippet (as expected) cause

Re: [CMake] if(MATCHES) broken??

Bill Hoffman wrote: Matthew Woehlke wrote: ping? I have created a bug report: http://public.kitware.com/Bug/view.php?id=8226 No ETA right now. Ok, thanks. -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- Microsoft, electricity, network connectivity. Fo

Re: [CMake] source_group() and solution directories

On Thu, Dec 4, 2008 at 4:48 PM, <[EMAIL PROTECTED]> wrote: > > Is it possible to have source_group() place files into > > a "solution directory"? This would be a folder directly > > under the solution instead of inside of a project. > > I'm confused, because I don't think of SOURCE_GROUP() as > pl

Re: [CMake] what is wrong with this snippet? (bug?)

Matthew Woehlke wrote: Matthew Woehlke wrote: set(!BANG wacky CACHE STRING "" FORCE) set("var with space" wacky CACHE STRING "" FORCE) message(STATUS "This is !BANG: ${!BANG}") message(STATUS "This is var with space: ${var with space}") The above snippet (as expected) causes a CMake error. What

Re: [CMake] if(MATCHES) broken??

Matthew Woehlke wrote: ping? I have created a bug report: http://public.kitware.com/Bug/view.php?id=8226 No ETA right now. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] what is wrong with this snippet? (bug?)

Matthew Woehlke wrote: set(!BANG wacky CACHE STRING "" FORCE) set("var with space" wacky CACHE STRING "" FORCE) message(STATUS "This is !BANG: ${!BANG}") message(STATUS "This is var with space: ${var with space}") The above snippet (as expected) causes a CMake error. What's interesting is that

Re: [CMake] Question about transitive dependencies

Robert Dailey wrote: In your sample code above, I noticed you didn't use add_dependencies(). Does target_link_libraries() guarantee build order when targets are specified instead of libraries? Yes. -Bill ___ CMake mailing list CMake@cmake.org http

Re: [CMake] if(MATCHES) broken??

Matthew Woehlke wrote: Bill Hoffman wrote: The problem is that if(something MATCHES something) works for either strings or variable names. The way that works is by checking to see if there is a variable defined by the string given to if. Even if that string is in quotes, it can still be trea

Re: [CMake] 'unset' not in --help-commands-list (also, attn: neundorf)

Philip Lowman wrote: On Tue, Nov 18, 2008 at 6:39 PM, Matthew Woehlke wrote: Need a bug opened for this or is it trivial enough to fix on the spot? unset appears to be in --help-commands and --help-command-list. Was this a bug? If so, how was it fixed? Not for me it doesn't? $ cmake --he

Re: [CMake] Question about transitive dependencies

On Thu, Dec 4, 2008 at 4:20 PM, Bill Hoffman <[EMAIL PROTECTED]>wrote: > Robert Dailey wrote: > > On Thu, Dec 4, 2008 at 4:06 PM, Alexander Neundorf < >> [EMAIL PROTECTED] > wrote: >> >>But, if you do in cmake: >>target_link_libraries(staticLibB staticLibA) >>

Re: [CMake] Question about transitive dependencies

Robert Dailey wrote: On Thu, Dec 4, 2008 at 4:06 PM, Alexander Neundorf <[EMAIL PROTECTED] > wrote: But, if you do in cmake: target_link_libraries(staticLibB staticLibA) this will not really link (as it would for a shared lib), but it will nevertheless

Re: [CMake] Question about transitive dependencies

target_link_libraries takes target names as its arguments as well as full paths to libraries. Just use CMake target names in target_link_libraries calls and do NOT use add_dependencies for libraries. add_dependencies is very useful for custom targets and custom commands to guarantee build order. I

Re: [CMake] [Fwd: Re: Why does dependency scanning in version 2.6 seem so slow?]

These are my results: All the details go below, but in two computers, both with cmake 2.6.0 (from the Ubuntu repositories), it takes ~ 50sec vs. 19sec to recompile when only one file changes... and the longest delay happens in the better PC, though the CPU's are very similar in speeds. Both cases a

Re: [CMake] Question about transitive dependencies

On Thu, Dec 4, 2008 at 4:06 PM, Alexander Neundorf <[EMAIL PROTECTED]>wrote: > But, if you do in cmake: > target_link_libraries(staticLibB staticLibA) > this will not really link (as it would for a shared lib), but it will > nevertheless keep track of the dependencies. > So when liking > target_li

Re: [CMake] Question about transitive dependencies

On Thursday 04 December 2008, John Doe wrote: > Hello, > > This discussion is based on my knowledge of the Gnu Compiler Collection. > > My understanding of the linking process is that B will never link > against A, because static libraries don't link against other static > libraries. Library B wil

Re: [CMake] Question about transitive dependencies

On Thu, Dec 4, 2008 at 3:47 PM, David Cole <[EMAIL PROTECTED]> wrote: > I think you're looking at Visual Studio project dependencies and not link > dependencies. It should not build *without* target_link_libraries calls. > They are necessary to get correct linker command lines. add_dependencies >

Re: [CMake] Question about transitive dependencies

I think you're looking at Visual Studio project dependencies and not link dependencies. It should not build *without* target_link_libraries calls. They are necessary to get correct linker command lines. add_dependencies does not link any libraries to anything, it just guarantees project building or

Re: [CMake] Question about transitive dependencies

On Thu, Dec 4, 2008 at 3:38 PM, Bill Hoffman <[EMAIL PROTECTED]>wrote: > Robert Dailey wrote: > >> Hi, >> >> Currently I have 3 projects named A, B, and C. A and B are both static >> libraries, and C is an executable. B depends on A, and C depends on B via >> add_dependencies(). When I generate a

Re: [CMake] Question about transitive dependencies

Robert Dailey wrote: Hi, Currently I have 3 projects named A, B, and C. A and B are both static libraries, and C is an executable. B depends on A, and C depends on B via add_dependencies(). When I generate a visual studio 9 project from this setup, how will the libraries be linked? The way I

Re: [CMake] Question about transitive dependencies

Hello, This discussion is based on my knowledge of the Gnu Compiler Collection. My understanding of the linking process is that B will never link against A, because static libraries don't link against other static libraries. Library B will have unresolved symbols when linking C. You must therefo

Re: [CMake] Question about transitive dependencies

On Thursday 04 December 2008, Robert Dailey wrote: > Hi, > > Currently I have 3 projects named A, B, and C. A and B are both static > libraries, and C is an executable. B depends on A, and C depends on B via > add_dependencies(). When I generate a visual studio 9 project from this > setup, how will

[CMake] Question about transitive dependencies

Hi, Currently I have 3 projects named A, B, and C. A and B are both static libraries, and C is an executable. B depends on A, and C depends on B via add_dependencies(). When I generate a visual studio 9 project from this setup, how will the libraries be linked? The way I want this to work is for C

[CMake] general question on documenting modules using the new FooConfig.cmake files

Hi, I've got a general question. Regular cmake FindFoo.cmake modules are documented by putting the docs at the top of the file. This documentation should list the variables, macros etc. provided by that module. Now if I switch to using FooConfig.cmake files and just very simple FindFoo.cmake f

Re: [CMake] How to make ctest not buffer its output?

On Thursday 04 December 2008, Hugo Heden wrote: > Good day all, > > I use ctest --build-and-test to do some stuff that takes a long time. > It seems that ctest buffers the output of its subcommands so that > nothing is written (to the "terminal") until at the end. This is a > little unconvenient --

Re: [CMake] [Fwd: Re: Why does dependency scanning in version 2.6 seem so slow?]

On Thursday 04 December 2008, Jose Luis Blanco wrote: > If this helps anyone, I'm working on a large project using CMake and in two > different computers, both with the same version of Ubuntu and cmake, it is > *REALLY SLOW* in only one of them while scanning dependencies, but it's not > in the oth

Re: [CMake] Getting a list of the defined CMake cache variables along with properties and documentation?

On Thursday 04 December 2008, Bartlett, Roscoe A wrote: > Hello, > > Is there a way in a CMakeLists.txt file to get a list of all of the defined > CMake cache variables, get their properties, and their documentation? I > would like to have this so that I can build more general documentation for >

Re: [CMake] Why does dependency scanning in version 2.6 seem so slow?

On Wednesday 03 December 2008, Senanu Pearson wrote: > Hi folks, > > Is there a way to speed up the dependency scan in version 2.6? > > I recently installed a new Linux OS (Mandriva 2009) which included an > upgrade to cmake 2.6 (I _think_ I had version 2.4 before). However, when If I remember cor

[CMake] source_group() and solution directories

Hi, Is it possible to have source_group() place files into a "solution directory"? This would be a folder directly under the solution instead of inside of a project. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] list( LENGTH ) problem

Le Wed, 3 Dec 2008 10:09:56 -0600, "Robert Dailey" <[EMAIL PROTECTED]> a écrit : > On Tue, Dec 2, 2008 at 3:00 PM, Alexander Neundorf > <[EMAIL PROTECTED]>wrote: > > > It expects a variable which holds a list: > > > > set(myList foo bar) > > list( LENGTH myList listlen ) > > message( ${listlen} )

[CMake] How to make ctest not buffer its output?

Good day all, I use ctest --build-and-test to do some stuff that takes a long time. It seems that ctest buffers the output of its subcommands so that nothing is written (to the "terminal") until at the end. This is a little unconvenient -- as a human I feel more comfortable actually seeing that "s

Re: [CMake] Invoke a target on a separate project in a generic way?

2008/12/4 Bill Hoffman <[EMAIL PROTECTED]>: > Hugo Heden wrote: >> >> Good day all, >> >> I am looking for a way within a CMakeLists.txt make sure that: >> >> -- at *build* time >> >> -- cmake is invoked on a *separate* project, and then also the >> "all"-target is invoked >> >> How do I do that? >

Re: [CMake] How does ctest impose CVS checkout time?

Bartlett, Roscoe A wrote: Hello, Does anyone know how CTest is able to set the CVS checkout time (with the -D option I would guess) when I am the one that provides the CVS checkout command in my Ctest script file by setting CTEST_CVS_CHECKOUT or CTEST_CVS_COMMAND? Is the CVS checkout follow

Re: [CMake] Can't get include() to work!

On Thu, Dec 4, 2008 at 6:53 AM, Bill Hoffman <[EMAIL PROTECTED]>wrote: > Robert Dailey wrote: > > >> The problem isn't about MAC line endings not working. I could care less >> about line ending requirements, I'll go with whatever works. The main >> problem I have is that CMake didn't TELL me what

[CMake] Pre-chekout configure vs. post-checkout configure

Hello, One of my nightly tests just failed last night because it tried to do a configure using outdated CMake files after I had enabled new options that caused it to fail. I need to understand how to make the nightly testing scripts more robust. Perhaps using extended Ctest scripting is the w

[CMake] How does ctest impose CVS checkout time?

Hello, Does anyone know how CTest is able to set the CVS checkout time (with the -D option I would guess) when I am the one that provides the CVS checkout command in my Ctest script file by setting CTEST_CVS_CHECKOUT or CTEST_CVS_COMMAND? Is the CVS checkout followed by some sort of 'cvs updat

[CMake] absolute include paths to resource compiler

>> Due to some weirdness in Visual Studio, I need to be able to give the >> resource compiler an absolute path: >> >> rc ... -I${CMAKE_SOURCE_DIR}/include >> >> If I put >> >> include_directories(${CMAKE_SOURCE_DIR}/include) >> >> CMake converts the absolute path to a relative one. >> >>

Re: [CMake] Invoke a target on a separate project in a generic way?

Hugo Heden wrote: Good day all, I am looking for a way within a CMakeLists.txt make sure that: -- at *build* time -- cmake is invoked on a *separate* project, and then also the "all"-target is invoked How do I do that? The following is a first rough sketch (that is not good enough, I believe

Re: [CMake] absolute include paths to resource compiler

[EMAIL PROTECTED] wrote: Due to some weirdness in Visual Studio, I need to be able to give the resource compiler an absolute path: rc ... -I${CMAKE_SOURCE_DIR}/include If I put include_directories(${CMAKE_SOURCE_DIR}/include) CMake converts the absolute path to a relative one. What is

Re: [CMake] How to find fortran library

Javier Gonzalez wrote: Maik Beckmann wrote: Am Mittwoch, 3. Dezember 2008 schrieb Javier Gonzalez: Hi all, I have a project that links to another project built with Fortran. My own project is a C++ project and I usually need to link against a fortran library of some sort to use the first on

Re: [CMake] Getting a list of the defined CMake cache variables along with properties and documentation?

Philip Lowman wrote: 1. A chicken and the egg problem, a configure has to occur and CMakeCache.txt created first before you can even parse it for documentation. Depending on the system being configured generation of a CMakeCache.txt can take some time due to all of the time needed to do comp

Re: [CMake] Can't get include() to work!

Robert Dailey wrote: The problem isn't about MAC line endings not working. I could care less about line ending requirements, I'll go with whatever works. The main problem I have is that CMake didn't TELL me what the problem was. It should have said, "Hey dummy, your line endings are unaccept

Re: [CMake] Future of debian package generator?

On Mon, Dec 1, 2008 at 2:38 PM, Johannes Dohmen <[EMAIL PROTECTED]> wrote: > Hi list, > > ok, my question is already in the subject. > > After some tests I like the idea of packaging debs with cmake [0] very much, > but I would like to know how the future plans for this feature are. > > I will desc

Re: [CMake] Invoke a target on a separate project in a generic way?

2008/12/4 Hugo Heden <[EMAIL PROTECTED]>: > Good day all, > > I am looking for a way within a CMakeLists.txt make sure that: > > -- at *build* time > > -- cmake is invoked on a *separate* project, and then also the > "all"-target is invoked > > How do I do that? > Before anyone else answers this:

[CMake] Invoke a target on a separate project in a generic way?

Good day all, I am looking for a way within a CMakeLists.txt make sure that: -- at *build* time -- cmake is invoked on a *separate* project, and then also the "all"-target is invoked How do I do that? The following is a first rough sketch (that is not good enough, I believe): ADD_CUSTOM_TARGE

[CMake] absolute include paths to resource compiler

Due to some weirdness in Visual Studio, I need to be able to give the resource compiler an absolute path: rc ... -I${CMAKE_SOURCE_DIR}/include If I put include_directories(${CMAKE_SOURCE_DIR}/include) CMake converts the absolute path to a relative one. -- /Jesper __

[CMake] absolute include paths to resource compiler

Due to some weirdness in Visual Studio, I need to be able to give the resource compiler an absolute path: rc ... -I${CMAKE_SOURCE_DIR}/include If I put include_directories(${CMAKE_SOURCE_DIR}/include) CMake converts the CMAKE_SOURCE_DIR absolute path to a relative one. Why? And how do I ge

[CMake] MSVC100?

I think this came up on the mailing list recently but I didn't couldn't find the thread To prevent the above abomination of a variable name ever being created by CMake when Microsoft releases version 10 of their wonderful compiler, I suggest doing away with the whole MSVC60 / MSVC70 / MSVC71 / MSV

Re: [CMake] How to find fortran library

Maik Beckmann wrote: > Am Mittwoch, 3. Dezember 2008 schrieb Javier Gonzalez: > >> Hi all, >> >> I have a project that links to another project built with Fortran. My >> own project is a C++ project and I usually need to link against a >> fortran library of some sort to use the first one. I use