stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Vitek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STDCXX-675) [MSVC] implement autolinking feature
Date Fri, 20 Jun 2008 00:29:45 GMT

    [ https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606604#action_12606604
] 

Travis Vitek commented on STDCXX-675:
-------------------------------------

There is also the issue that we don't always know what the name of the library is going to
be. The user may select a different name for the library (by changing the project file or
possibly renaming the file directly). If this happens, then the autolink will cause the linker
to look for a library file with the wrong name. In order to get it working again, they would
need to {{#define _RWSTD_NO_EXT_AUTOLINK}} or modify {{_autolink.h}}. The problem is that
they may spend hours trying to figure out where the reference to the library is coming from.

What real utility does this provide? The user still needs to set the library path so that
the given library is found. Perhaps a better idea would be to add a blurb to the documentation
telling the user about the option to use the {{#pragma}} in their code?



> [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.


Mime
View raw message