[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost-build
Subject:    Re: [Boost-build] [Getting started] Building with
From:       Vladimir Prus <ghost () cs ! msu ! su>
Date:       2007-06-30 16:08:59
Message-ID: E1I4fVL-0006M0-Me () zigzag ! lvk ! cs ! msu ! su
[Download RAW message or body]

John Maddock wrote:

> 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]) ;

tools/jam/src/build.jam only affects building bjam itself. You
seem to have it already built, so at this point, what's written in
that file does not matters.

If you need to pass extra option to a compiler, you can do
it in user-config.jam. Please see the "builtin tools" section
in boost.build docs (http://boost.org/boost-build2)

- Volodya



[prev in list] [next in list] [prev in thread] [next in thread]