Return-Path: Delivered-To: apmail-stdcxx-issues-archive@locus.apache.org Received: (qmail 17648 invoked from network); 23 Jun 2008 14:17:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jun 2008 14:17:36 -0000 Received: (qmail 75310 invoked by uid 500); 23 Jun 2008 14:17:38 -0000 Delivered-To: apmail-stdcxx-issues-archive@stdcxx.apache.org Received: (qmail 75287 invoked by uid 500); 23 Jun 2008 14:17:37 -0000 Mailing-List: contact issues-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list issues@stdcxx.apache.org Received: (qmail 75276 invoked by uid 99); 23 Jun 2008 14:17:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jun 2008 07:17:37 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jun 2008 14:16:56 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 169DB234C147 for ; Mon, 23 Jun 2008 07:16:45 -0700 (PDT) Message-ID: <1442595368.1214230605091.JavaMail.jira@brutus> Date: Mon, 23 Jun 2008 07:16:45 -0700 (PDT) From: "Farid Zaripov (JIRA)" To: issues@stdcxx.apache.org Subject: [jira] Commented: (STDCXX-675) [MSVC] implement autolinking feature MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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.