[CMake] Windows library target names

[J Decker]

I'll add my two cents - I like that the names are the same, it allows
me to switch the release out with the debug and not have to recompile
the executable.  Besides, I doubt your interface changes because of
debug or release mode - so the .lib should be exactly the same.
Though I suppose if you pass extra parameters for debugging like
__FILE__,__LINE__ then C++ name mangling would get upset.  But even
visual studio itself starts building the same name'd output files -
you have to manually update the project to get a different out - which
was already given as a solution - test if you're buliding debug mode,
and set the suffix appropriately.

On Thu, Jul 22, 2010 at 1:54 PM, Olaf van der Spek <olafvdspek at gmail.com> wrote:
> On Thu, Jul 22, 2010 at 10:46 PM, Michael Jackson
> <mike.jackson at bluequartz.net> wrote:
>> Ya know , I go back and forth on this. In my own projects I will give my
>> libs a _debug suffix because I end up installing both debug and release into
>> a local directory and my FindXXX.cmake scripts know to look for both a debug
>> and release version of the library, ala, FindQt4.cmake. I like the way Qt
>> does this and so went with TrollTech's "standard".
>>  If you don't have all the infrastructure to do that then NOT having any
>> default naming is the best way.
>
> What do you mean?
> Using the same name for all configs?
> Shown by your own example, that doesn't work.
>
> Olaf
> _______________________________________________
> 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