[
https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607242#action_12607242
]
Farid Zaripov commented on STDCXX-675:
--------------------------------------
The STLport and boost both are using this feature. This feature is useful when
you make the library files for all build modes in the same directory (like
STLport and boost does). Then you have to specify this path to the linker and
linker itself select the proper library file.
Of course when you have library files for different build modes in their
distinct directories and you have to specify the path of the concrete library
for some build mode this feature is looking as redundant.
> [MSVC] implement autolinking feature
> ------------------------------------
>
> Key: STDCXX-675
> URL: https://issues.apache.org/jira/browse/STDCXX-675
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 4.1.2, 4.1.3, 4.1.4, 4.2.0
> Environment: MSVC, ICC/Windows
> Reporter: Farid Zaripov
> Assignee: Travis Vitek
> Priority: Trivial
> Fix For: 4.3
>
> Attachments: autolink.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> At the moment the users of the library should explicitly specify the used
> library name in linker command line. Here might be problems if the user's
> project was compiled with config.h for some configuration (let's say 12d) but
> linked with library for another configuration (i.e. libstd12s.lib).
> The MSVC and ICC/Windows has the posibility to specify the library using
> #pragma comment (lib, libname) directive. So #including any header from the
> library will leads to linking automatically with the proper library file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
