Re: [jamboost] static lib extension on windows

From: David Abrahams (dave_at_[hidden])
Date: 2002-12-02 08:33:02

Vladimir Prus <ghost_at_[hidden]> writes:

> David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> 
>> 
>>>Somewhere in builtin.jam, I see
>>>
>>> declare-type NT : STATIC_LIB : a : LIB : main ;
>>>
>>>Hmm.. One thing sure: borland compiler won't work
>>>with it (I'm just adding support for it). So, why this
>>>line is there? Is ".a" a common suffix for gcc on NT?
>> 
>> 
>> For Cygwin GCC, that's right.
>
> Ick! Can it handle "lib", so that we don't have to implement
> per-toolset suffix right now?

Yes, though Cygwin users will dislike it.

>>>In this case, will be need to be able to determine suffix
>>>based on os/toolset combination?
>> 
>> 
>> It's not required, but desirable. You can optionally generate import
>> libraries with Cygwin GCC, and those should have extension
>> ".dll.a". Believe it!
>
> Fancy!

Furthermore, NT python extensions can be called ".dll", but they
should be called .pyd (or "_d.dll" and "_d.pyd" for the debug
version)... Unless they were built with Cygwin GCC, in which case they
must target the Cygwin version of Python and can only use ".dll".

> OK, filed
>
> http://zigzag.cs.msu.su:7814/scarab/issues/id/BB14
>
> Have to implement new system libraries interface before turning
> to it.

OK.

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution