Re: [CMake] CMAKE_BUILD_TYPE case sensitivity
> > I see that this CMake variable is not case-sensitive at it and defaults to > DEBUG. I'm afraid this is incorrect; the default build type is empty. When you build with Release, the flag NDEBUG is set; when you build with Debug the DEBUG flag is set. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Specifying linker dependencies based on a new configuration type for vs2010
Hi all, I've setup a new build configuration called ReleaseLowOpt for a set of projects we're developing. Currently I have all the linker / compiler options being set, my problem comes when I'm determining the set of libraries to specify on the link line and which directory to pull them from. Our current structure is a large set of Core libraries that are installed into a directory according to which build configuration it's being built under (Debug / Release / ReleaseLowOpt). For the executables linking against these Core Libraries, we have a CMake function that goes through the Core Library directories and enumerates them, adding each to the linker line. For instance, all libraries under %CoreInstallDirectory%/Debug/ will be put into the Debug linker line for the executable, same process for the Release configuration. It does this through the *debug* and *optimized* keywords, but now I need to specify them for the ReleaseLowOpt configuration. I've been researching this for a little while and it seems that there are certain Target properties I could use, like IMPORTED_LINK_INTERFACE_LIBRARIES_ , but I can't seem to get that to make any difference in my link line. As a separate topic, I'm curious to understand how Target properties play into the greater structure of CMake, so I can make my code flow a bit better. Thanks for your time, Dan Sibbernsen -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.11 Released!
Hei hei, On Fri, May 17, 2013 at 11:09:11AM -0400, Robert Maynard wrote: > - target_link_libraries(myexe yourlib) can now build myexe sources > with requirements specified Does this mean transitive linking between separate projects is possible? Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** pgpVSWAH_Mwfr.pgp Description: PGP signature -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Creating a common (= across several projects) CMake module/include-file/library
Hei hei, On Mon, May 13, 2013 at 06:17:58PM -0400, Matthew Woehlke wrote: > Another option to consider is keeping the file in an external > repository and using your VCS's external-repo support to bring it > into your other projects. This way the file exists in your source > tree, but your VCS is tracking it against a central repository, > rather than each project's repo having independent copies. (This > will also probably make getting the file into your source packages > easier.) We do this with git submodules and adding the path of this subdirectory to the cmake paths like you described. Works pretty well. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** pgpS98arMlF2F.pgp Description: PGP signature -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
