[
https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609770#action_12609770
]
Travis Vitek commented on STDCXX-675:
-------------------------------------
I agree. I don't see this as useful for our users.
If we are really worried about them using libraries and headers from different
configurations, we could generate a symbol name based on the configuration. The
library would export the symbol and one of the library headers would import it.
That way the executable won't link if the library and headers are from
different configurations.
> [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.
