Re: [Boost-build] Cygwin static build run from the Windows command line fails

Subject: Re: [Boost-build] Cygwin static build run from the Windows command line fails
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-02-23 11:39:39

AMDG

On 02/23/2016 09:07 AM, Beman Dawes wrote:
>> Are you doing this from cygwin shell with cygwin build of b2 or from
>> Windows shell with msvc build of b2, or something else?
> 
> Windows shell with msvc build of b2
> 

  It's been a while since I used cygwin,
but I always ran an msvc build of b2
from the cygwin shell.

>> It seems that you actually use Windows shell with cygwin gcc, so when
>> Boost.Build asks gcc where its toolchain is installed it reports /usr, and
>> that clearly does not work in Windows shell.
>

  python.jam has code to handle the path
conversion.  Would there be any problems
if we attempt to detect unix-style paths
and translate them?  Can a non-cygwin
gcc ever return paths starting with '/'
from -print-prog-name?  Is there any way
for a cygwin gcc to return a cygwin path
that doesn't begin with '/'?  Is it possible
for a cygwin gcc to return windows paths?
If we check both paths, can they both exist
and cause us to choose the wrong one?
Would $(flavor) != mingw && [ os.name ] == NT
be a correct test?

> Could I create user-config.jam entries for ar and ranlib?
> 

<ranlib> and <archiver>

>> Do you have a particular reason for using cygwin? If you would like to
>> test with gcc, would not mingw make for a more convenient option?
>>
> I do have mingw installed, and use it for some testing. But the mingw
> distributions I've tried do not handle exceptions correctly, so my
> exception handling tests in filesystem and system libraries fail, and
> that's irritating.
> 

In Christ,
Steven Watanabe