Boost logo

Boost-Build :

From: Zbynek Winkler (zwin_at_[hidden])
Date: 2004-03-31 06:20:30

Vladimir Prus wrote:
>>Could an improved version of this be committed to CVS? If not, what are
>>the complications?
> There are two problems:
> 1. It's not possible to specify 'nocygwin' if you also specify the location of
> the compiler.
> 2. I'm not sure that specifying 'nocygwin' in 'using' is good idea. The
> 'using' util now was used only to specify where to find the compiler, but not
> what flags it should use. You can put this in your top-level Jamfile:
> project
> : requirements <cflags>-mno-cygwin <linkflags>-mno-cygwin
> ;
> to achieve the same effect. What do you think?

Well, the question was not for me but I'll answer anyway ;-)

This way I would not be able to compile the project with a compiler that
does not recognize the flag. I could restrict it only to gcc using
conditional properties like this:
<toolset>gcc:<linkflags>-mno-cygwin <toolset>gcc:<cflags>-mno-cygwin
but I guess when gcc is really mingw or when on linux, this could cause
problems. So from my point of view gcc with -mno-cygwin is different
compiler so specifying it in 'using' is a good idea. Not sure about the
way though... It could be something similar to versions. It would allow
using <toolset>gcc when there are no other versions and
<toolset>gcc-nocygwin when there are more...


PS. I can compile my project with 'bjam toolset=gcc,msvc-6.0,msvc-7.1'
on windows while my colleague uses 'bjam toolset=gcc' on linux. The gcc
on windows is mingw so there is no problem. Could be cool to add
gcc-cygwin, and gcc-nocygwin to the list for the windows platform (but
not really important).

Faculty of Mathematics and Physics, Charles University, Prague, Czech 

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at