MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011030CMakeCMakepublic2010-07-22 18:052010-12-14 18:50
ReporterOlaf van der Spek 
Assigned ToDavid Cole 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionCMake 2.8.3Fixed in Version 
Summary0011030: Decorate library names
DescriptionIt'd be great if library names could be decorated. That way, all files can be stored in a single lib dir from which the linker can pick the right variant.

The decoration should specify:
Debug vs Release
Dynamic vs Static
Dynamic vs Static Runtime
x86 vs x64
Compiler (maybe)
Threading (maybe)

See for example http://www.boost.org/doc/libs/1_43_0/more/getting_started/windows.html#library-naming [^]
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-07-22 18:05Olaf van der SpekNew Issue
2010-07-29 12:47Brad KingNote Added: 0021554
2010-07-29 12:48Brad KingStatusnew => closed
2010-07-29 12:48Brad KingResolutionopen => won't fix
2010-07-29 13:25Olaf van der SpekNote Added: 0021557
2010-07-29 13:25Olaf van der SpekStatusclosed => feedback
2010-07-29 13:25Olaf van der SpekResolutionwon't fix => reopened
2010-08-25 07:43David ColeStatusfeedback => assigned
2010-08-25 07:43David ColeAssigned To => David Cole
2010-08-25 07:46David ColeNote Added: 0021945
2010-08-25 07:46David ColeStatusassigned => resolved
2010-08-25 07:46David ColeResolutionreopened => won't fix
2010-08-31 18:13David ColeTarget Version => CMake 2.8.3
2010-12-14 18:50David ColeNote Added: 0024100
2010-12-14 18:50David ColeStatusresolved => closed

Notes
(0021554)
Brad King   
2010-07-29 12:47   
The OUTPUT_NAME and OUTPUT_NAME_<CONFIG> target properties

  http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:OUTPUT_NAME [^]

provide all the tools needed to do this. Each project will define its own scheme for this; we do not want to offer or enforce one.
(0021557)
Olaf van der Spek   
2010-07-29 13:25   
As a hypothetical library developer, I've no idea about platform-specific naming conventions. I don't want to have any idea about this either.
What's the reason to require every single lib dev to duplicate this code?
I think a scheme should at least be offered!
(0021945)
David Cole   
2010-08-25 07:46   
This is beyond the scope of what CMake offers.

If you think a scheme should be offered, then offer a scheme in the form of a well-tested patch to the CMake source tree.

There is no concensus about this issue on the CMake mailing list among its current heavy users. Therefore, there is no "right way" to address this.

If a scheme that could be generally agreed upon could be offered, then we could consider adding this feature. Until that happens, none of the core CMake devs are really interested in spending their time on developing this feature.

The basic functionality to allow you to name things according to your chosen scheme is there and works everywhere that CMake works. (See previous notes in this bug.)

Choosing your scheme is up to you.
(0024100)
David Cole   
2010-12-14 18:50   
Closing bugs that have been resolved for more than 3 months without any further updates.