[CMake] Config Dependent Link Paths

[aaron.meadows at thomsonreuters.com]

I had seen that option, which is for a specific library, I was hoping to just be able to selectively set the library path for a particular configuration.  The current configuration relies heavily on #pragma comment(lib,"libraryname.lib") to automatically build the library link list.  That's probably going to have to be gutted to move to linux, but I was hoping to get a solution going faster, and this seems to be the only thing left to convert all 80 projects. 

If that's the only way, that's the way I'll pursue, but if anyone knows how to change that link path, I would really appreciate it.

Thanks for the help!

--aaron 


-----Original Message-----
From: Eric Noulard [mailto:eric.noulard at gmail.com] 
Sent: Wednesday, August 19, 2009 2:50 PM
To: Meadows, Aaron C.
Cc: CMake ML
Subject: Re: [CMake] Config Dependent Link Paths

2009/8/19  <aaron.meadows at thomsonreuters.com>:
> Background:
>        * I am moving from Visual Studio 2008 projects to Cmake in 
> preparation
>          for porting our software to Linux.
>
>        * We have debug and release versions of 3rdparty libraries to 
> link
>          against in two separate paths but under the same name.
>                (debug/library1.lib & release/library1.lib are debug 
> and
>                release builds of the same library)
>
> Question:
>        With the "multi-configuration generator" for Visual Studio, how 
> can I configure my root CMakeList.txt file to setup these two separate 
> link paths based on which configuration is used?

I did not tried this but

target_link_libraries(<target> [lib1 [lib2 [...]]]
                             [[debug|optimized|general] <lib>] ...)

may be used to specify specific library like in:

target_link_libraries(myapp debug /full/path/to/debug/library1.lib) target_link_libraries(myapp optimized /full/path/to/release/library1.lib)



--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org


This email was sent to you by Thomson Reuters, the global news and information company.
Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.