Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Message-ID: <9339162.1196225923721.JavaMail.jira@brutus>
Date: Tue, 27 Nov 2007 20:58:43 -0800 (PST)
From: "Martin Sebor (JIRA)" <jira@apache.org>
To: stdcxx-dev@incubator.apache.org
Subject: [jira] Commented: (STDCXX-336) allow multiple config.h files in the
 same installation directory
In-Reply-To: <23243236.1170961625511.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/STDCXX-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546110 ] 

Martin Sebor commented on STDCXX-336:
-------------------------------------

Not sure renaming the generated $BUILDDIR/include/config.h to include the name (and possibly version) of the compiler along with the build type would be a forward compatible change...

> allow multiple config.h files in the same installation directory
> ----------------------------------------------------------------
>
>                 Key: STDCXX-336
>                 URL: https://issues.apache.org/jira/browse/STDCXX-336
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 4.1.2, 4.1.3, 4.1.4
>         Environment: all
>            Reporter: Andrew Black
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> A useful enhancement could be the ability to install multiple versions of the standard library into the same location.  While there is nothing in the makefiles that would prevent such an installation, a problem arises with the config.h file in the include sub directory of the install directory.  Only one config.h file can reside in this location at a time, and different versions (such as those generated when characterizations are run with different compilers) may differ.
> One problem that needs to be considered in implementing (or deciding not to implement) this request is the situation where a config.h file hasn't been generated for a particular os/compiler/buildtype/buildtag.
> Another problem to consider is when you have the same os/buildtype/buildtag, but different compilers, and one or both compilers support features that the other doesn't.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.