Re: [Boost-build] Disabling library build on a single platform

Subject: Re: [Boost-build] Disabling library build on a single platform
From: Jeremiah Willcock (jewillco_at_[hidden])
Date: 2012-04-16 15:45:11

On Mon, 16 Apr 2012, Vicente J. Botet Escriba wrote:

> Le 16/04/12 21:13, Jeremiah Willcock a écrit :
>> On Mon, 16 Apr 2012, Vicente J. Botet Escriba wrote:
>> 
>>> Le 16/04/12 19:51, Jeremiah Willcock a écrit :
>>>       The bug report at <URL:https://svn.boost.org/trac/boost/ticket/5606> 
>>> suggests Boost.Graph disabling its build on Sun compilers.  How do I do 
>>> that?
>>> 
>>> Hi,
>>> 
>>> is Boost.Xpressive essential to Boost.Graph?If yes, stop reading.
>>> 
>>> If not, I would expect that the parts depending on Boost.Xpresive can be 
>>> excluded conditionally. Couldn't this be better that forbidding Sun users 
>>> to use Boost.graph?
>> 
>> It's not essential, and is used in a header that most parts of Boost.Graph 
>> don't include by default.  The Sun compiler breaks on many other parts of 
>> Boost.Graph as well, though, so I'm not too concerned about portability to 
>> it (most of the Sun compiler regression test errors have nothing to do with 
>> Xpressive).  The IBM compiler seems to break on PropertyTree as well, which 
>> is used for GraphML input.  Those are the two major compilers that fail 
>> large parts of BGL; my opinion is just to avoid building the boost_graph 
>> library rather than trying to only compile those parts of it that aren't 
>> broken.
> I understand. If what you want is to show this on the regression tests, 
> update the status/explicit-failures-markup.xml
>
> <library name="thread">
> <mark-unusable>
> <toolset name="*como-4_3_3*"/>
> <note author="B. Dawes" refid="10"/>
> </mark-unusable>
>
> If what you want is to avoid the build completely, I could not help you too 
> much. Perhaps you could define a specific rule that uses
>
>    if ! <toolset>sun in $(properties)
>    {
>      ...
>    }
>
> At a last resort you could add some code to report a clear error when 
> __SUNPRO_CC is defined.

It sounds to me like the best solution is just to close that bug as 
wontfix.  Is that reasonable?  Are there other libraries that are 
auto-skipped on platforms where they don't build?

-- Jeremiah Willcock