Re: [Boost-build] [boost] [Boost][Python] Fails for gcc-cygwin-3.4.4

From: David Abrahams (dave_at_[hidden])
Date: 2007-02-21 15:51:12

Roland Schwarz <roland.schwarz_at_[hidden]> writes:

> David Abrahams wrote:
>>    That is,
>>    when building from a cygwin bjam, the default would be not to pass
>>    -mno-cygwin, and when building from a Win32 bjam, 
>
> Sorry don't understand. What exactly do you mean by a "cygwin bjam" or 
> "win32 bjam"?

I mean a bjam that was itself built under cygwin or win32, and meant
to be run from either the cygwin bash shell or the win32 CMD shell,
respectively.

> What would be the default when I invoke 

Invoke bjam?

> from CMD.EXE (I guess win32 bjam, but could also be cygwin bjam)

The former.

> using C:\Cygwin\bin\g++.exe?

Using how?

If bjam were invoked from CMD.EXE, the default would be to pass
-mno-cygwin.

>> the default would
>>    be to pass -mno-cygwin.  In either case, the default would be
>>    overridable by passing target-os=...
>
> Hmm, would this allow e.g
>
>    bjam toolset=gcc-3.4.4-cygwin,gcc-3.4.4 stage
>
> if I want both cygwin and "native" target os?

Something like that.

>> * If we drop the ability to arbitrarily choose a version string, we
>>   need a way to identify different configurations of a toolset that
>>   may have the same version number.  For example:
> [snipped examples]
>>   The solution we came up with is to add an optional argument to
>>   "using" that allows you to create a special toolset subfeature
>>   on-the-fly, something like:
>> 
>>       using gcc : 3.4 : /usr/local/conceptgcc/bin/g++ : conceptgcc ; 
>> 
>>   This feature could then also be used to identify the toolset on the
>>   command-line, something like:
>> 
>>      bjam toolset=conceptgcc
>> 
>
> We need something
>
> 1) library authors can use to mark up in explicit-failures-markup.xml
> 2) library authors can use in Jamfiles.

For both they can use the primary toolset name and build properties.

> For 1) a kind of simple pattern matching is
> available. e.g. gcc-cygwin*

  gcc-3.4/target-os=cygwin

> (Will the subfeature be visible in this context?)

Which context?

> For 2) a similar substring matching sometimes looks advantageous. But I 
> do not know if this just would be kind of opening Pandoras box.

Sorry, I'm not sure what you're driving at.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com