|
Boost-Build : |
From: John Maddock (john_at_[hidden])
Date: 2007-06-30 12:03:15
Vladimir Prus wrote:
> John Maddock wrote:
>
>> In following up the attached message the cause appears to be a
>> Boost.Build issue because specifying:
>>
>> bjam --toolset=gcc-nocygwin
>>
>> has no effect on the gcc command line,
>
> Should it? I'm not aware of this "-nocygwin" syntax,
> so unless somebody else has implemented it, it does not work.
Well I hadn't heard of it either, but build.jam contains:
## GCC 2.x, 3.x on CYGWIN but without cygwin1.dll
toolset gcc-nocygwin gcc : "-o " : -D
: -s -O3 -mno-cygwin
[ opt --release : -finline-functions ]
[ opt --debug : -s -O3 -fno-inline -pg ]
-I$(--python-include)
: -L$(--python-lib[1]) -l$(--python-lib[2]) ;
But the -s -O3 -mno-cygwin options don't appear to get propagated - should
they?
Thanks, John.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk