Re: [Boost-build] cygwin builds are running with wrong tagging

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2007-02-10 13:07:01

Sorry for repeatedly answering my own posts, but since none seems
to care, I just let others know about progress...

Roland Schwarz wrote:

> 1) In a single user-config.jam it is not possible to specify both,
>     a mingw _and_ a cygwin compiler. (This is what I tried to do.)

This seems to be true, but I suspect this should be possible, and just 
is prohibited by a bug in the (mingw) tagging code.

> 2) The cygwin build is only possible from within a bash. Dave's "getting
>     started" is wrong in this respect. (cygwin build cannot be done from
>     cmd.exe)

I was wrong in this assumption. The problem is, that Boost.Build will 
not automatically set up the PATH variable to point to the g++ dir.
One will not notice this "bug" if the PATH already contains the dir to 
the (correct) g++. I again suspect this to be a bug in gcc.jam

> 3) When setting up a cygwin _and_ mingw on the same machine, one must
>     take care that %HOMEDRIVE%%HOMEPATH% does not point to the same
>     directory that $HOME (in bash) does. I.e. you need two _distinct_
>     user-config.jam each only responsible for a different flavor of
>     compiler.

I suspect 3) to be not necessary, once the above 2 problems have been 
resolved.

I came over yet another issue: When b uilding on cygwin, where should 
the site-config.jam be searched: In %SystemRoot% or in /etc ?

I will further investigate the problem.

Roland