From: David Abrahams (dave_at_[hidden])
Date: 2003-01-09 10:18:13
Vladimir Prus <ghost_at_[hidden]> writes:
> David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>>>David Abrahams wrote:
>>>>-declare-type NT : STATIC_LIB : a : LIB : main ;
>>>>+declare-type NT : STATIC_LIB : a : LIB : main ; # this is a lie, should be lib.
>>>> declare-type : STATIC_LIB : a : LIB : main ;
>>>Just to clarify: should this really be "lib"?
> OK, changed.
>>>Even for cygwin?
> OK, made gcc toolset use "a" suffix on all platforms.
Not sure what's appropriate for MinGW gcc. I think when you use -lfoo
with MinGW, it looks for libfoo.a, but I'm not sure. If you want to
build libs compatible with other Windows toolsets (is that even
possible with MinGW?) you'll need ".lib"
>>>As I recall, just a few days ago Pavol Droba has complained on
>>>Boost ml that "lib" extension is not regognized by cygwin...
>>>Or are NT and CYGWIN different things?
>> Yes. That's why both names appear in that file.
> What are the differences, when one uses the gcc toolset?
CYGWIN is a platform and an environment that runs on top of NT and
gives the illusion of Unix. A bjam built under Cygwin will be
different from one built under NT.
GCC is a separate issue; you can use the Cygwin GCC or the MinGW GCC
from NT. From Cygwin, you can only use Cygwin GCC. The difference
between Cygwin and MinGW GCC is which runtime and system libraries
they link to. Cygwin GCC uses the Cygwin Unix emulation layer
library, whereas MinGW uses the native libraries.
-- David Abrahams dave_at_[hidden] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
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