[
https://issues.apache.org/jira/browse/STDCXX-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-336:
--------------------------------
Priority: Critical (was: Minor)
Environment: all
Summary: allow multiple config.h files in the same installation
directory (was: Desire capacity to have multiple config.h files in an install
directory)
This is important if we want to allow multiple configurations of the same
library to coexist in the same directory as users of the Rogue Wave
implementation are accustomed to doing. Bumped up priority to Critical.
> 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
> Environment: all
> Reporter: Andrew Black
> Priority: Critical
> Fix For: 4.2
>
>
> 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.
