[
https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547221
]
Farid Zaripov commented on STDCXX-675:
--------------------------------------
ChangeLog:
STDCXX-675
* include/rw/_autolink.h: New header file to enable autolinking feature.
* include/rw/_config-msvcrt.h: #include _autolink.h.
* src/export.cpp: Added missing #define _RWSTD_LIB_SRC macro.
The _autolink.h file is intended to be #included in _config.h, but since this
feature is supported by only MSVC and ICC/Windows, it #included in
_config-msvcrt.h.
> [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.
