ansaurus

Question

CMake: defining link directories and libraries for different build targets

Answer 1

A:

you can simply invoke cmake with the configuration set already:

cmake -DCMAKE_BUILD_TYPE="Debug"

or what I do is specify link and platform on command line, then adjust configuration type manually:

cmake -dMyConfigType="DebugStaticX86"

#CMakeLists.txt
if( ${MyConfigType} STREQUAL "DebugStaticX86" )
  set( CMAKE_BUILD_TYPE Debug )
  set( MyLinkType Static )
  set( MyPlatform x86 )
  #now include other files that set the actual compile/link options
  #depending on values of MyLinkType and MyPlatform
  ....
endif

stijn 2010-09-30 10:52:10

Well, but I want to create one the .vcproj files with the Release and Debug configurations in it. If I do it that way, I will have a project file with only either the debug or the release configuration in it?

Spooky 2010-10-04 07:32:36

as far as I know, yes. Don't think it;s possible to have cmake generate more than one configuration at a time, and that affects all ouputs not only vcproj.

stijn 2010-10-04 07:56:52

Well, CMake is capable of doing that. For instance, I can use CMAKE_CXX_FLAGS_DEBUG and CMAKE_CXX_FLAGS_RELEASE (or however the configuration is named) in order to specify compiler flags for each configuration. I thought that there would be a way for other options too, for the linker for instance.

Spooky 2010-10-04 13:46:05

the way tibur shows should do that, but you're still left with a vcproj containing only debug or release, not both.

stijn 2010-10-04 13:51:27

Answer 2

+1 A:

There is a target_link_libraries option that helps you to do that. But you will need to expand your library name to full path.

target_link_libraries(foo
  debug c:/path/to/debug/lib/blah.lib 
  optimized c:/path/to/optimized/lib/blah.lib)

If your library location is named the way CMake do it (Debug/MinSizeRel/RelWithDebInfo/Release), you can use the VS $(ConfigurationName) variable:

link_directories(c:/path/to/all/libs/$(ConfigurationName)/)

Beware, $(ConfigurationName) is not a cmake variable: it will only be expanded by VS during the build/link step.

tibur 2010-09-30 11:42:12

Hm, what exactly is CMake creating, if I use TARGET_LINK_LIBRARIES? Is CMake breaking the path apart and writing the information into the project file separately to the library folder and library files?

Spooky 2010-10-04 07:33:14

If you specify a full path for a library in the `target_link_libraries` command, it will add the library name with its full path into the library files field. I usually don't use `link_directories` command. My answer was: use `target_link_libraries` with debug and optimized keywords **or** use `link_directories`.

tibur 2010-10-04 11:35:28

I see. However, I do have another problem with TARGET_LINK_LIBRARIES. I don't exactly know what to put into the first argument. It may be hard to describe for me what exactly the problem is, since I still do not fully understand, how CMake is set up for this project (someone else made it and now I have to work with it/change something).I think the problem is, that one CMakeLists.txt file is used by 2 projects, which are named differently, and thus I can't use one TARGET_LINK_LIBRARIES( foo debug ... ) call.

Spooky 2010-10-04 13:47:43

The first argument of `target_link_libraries(MyProgram ...)` (the standard is to use lower case for cmake functions, now) is the name of the program (not the project) you are compiling using `add_executable(MyProgram ...)`.

tibur 2010-10-04 20:12:15

ansaurus

tags:

views:

answers:

CMake: defining link directories and libraries for different build targets

related questions