[
https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552933
]
Travis Vitek commented on STDCXX-675:
-------------------------------------
If the new user takes advantage of the autolinking feature, they will have to
modify their build system to get it to work with a previous version of the
library. i.e. they will need to explicitly link the library file when they go
back to 4.2.0.
Will this ever be useful for any compiler other than MSVC and ICC/Windows? Is
there a way that we can ensure the user links the right library on all
platforms? This wouldn't avoid the need to explicitly link the library, but it
would eliminate issues with linking the wrong library.
> [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: Farid Zaripov
> Priority: Trivial
> Fix For: 4.2.1
>
> Attachments: autolink.patch
>
>
> 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.
