[CMake] libraryname decoration

[J Decker]

Well let's look at how some things are handled.

direct X has multiple version of the same library, and msvcrt
(msvcrtd)... these are name mangled things.

.NET has moved to keeping seperate directories where everything is
exactly the same name.

Surely there's more than one paradigm that can be used, but it's up to
the developer of the library system...

most 'normal' builds of open source projects produce a single build
mode - release OR debug OR ...; and they maintain a compatible
interface so peices of release code can be built against debug
libraries and vice versa;

Visual studio and probably eclipse and code blocks can generate
multiple builds at the same time, but it turns out that cmake really
only spits out one of the modes, since it doesn't re-evalute
cmakelists to figure out what the real definitions are for each mode;
so really cmake is only producing a single target anyhow.



On Fri, Jul 30, 2010 at 6:19 AM, Olaf van der Spek <olafvdspek at gmail.com> wrote:
> On Fri, Jul 30, 2010 at 2:58 PM, Michael Jackson
> <mike.jackson at bluequartz.net> wrote:
>> And what if someone else is using a different naming decoration for
>> their project than what is in the auto-link headers? Then you have to
>> update all those headers to your own naming scheme which amounts to a
>> fork of that project. Which sucks.
>
> Why would you change the naming scheme of your dependencies?
> You could just disable auto linking and you're back at where you are now.
>
> 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
>