Re: [boost] [build] adding a rquirement for Cygwin only?

Subject: Re: [boost] [build] adding a rquirement for Cygwin only?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2015-03-05 14:07:32

AMDG

On 03/05/2015 11:08 AM, Peter Dimov wrote:
> Steven Watanabe wrote:
>> Last time I used Cygwin (which was admittedly a long time ago) I put
>> something like this in my user-config.jam:
>>
>> import toolset ;
>> using gcc ;
>> toolset.add-requirements <toolset>gcc:<target-os>cygwin ;
> 
> This would work if the only gcc on my system were Cygwin, and I probably
> could live with it, but it won't work in the case in which I also have
> MinGW and what gcc is used depends on the current PATH. Which is why I
> was somehow trying to make it autodetect.
> 

It takes a bit of hacking to make MinGW and
Cygwin coexist.  I know I did it once upon
a time, but I don't remember the details.
Autodetection would be great, but doing it
right will probably be a fair amount of work.

>> Actually... I seem to recall that Boost.Thread's Jamfile doesn't work
>> correctly even if target-os is set.  It sets the default threadapi
>> entirely based on the host.
> 
> That's probably because nobody ever sets target-os. :-)
> 
> (There are other places that don't handle cross-compilation properly,
> using host-os when target-os would be correct. Most people are probably
> entirely unaware of the distinction. I admit I was.)
> 

In Christ,
Steven Watanabe