Re: [jamboost] dll prefixes + imp libraries under cygwin

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-04-13 17:13:32

sijuju2001 wrote:

> I have been experimenting with using bjam as an alternative to a
> make-based build system for an open source project. The original make
> system uses the following (seemingly standard) naming convention for
> cygwin targets:
> 
> static lib: libfoo.a
> import lib: libfoo.dll.a
> dll : cygfoo.dll
> 
> However, from what I can tell both v1 and v2 of the bjam cygwin
> toolsets (which shipped in boost 1.31.0) use the following different
> convention:
> 
> static lib: libfoo.a
> import lib: <not created>
> dll : libfoo.dll
> 
> Is this correct? If so, do you know how would I go about generating
> the implib and the final build target with the appropriate name?

That is not supposed to be correct? That is, if it's not generating the 
implib, it's a bug. The generation, for v1 should be:

static lib: libfoo.lib
import lib: foo.lib
dll : foo.dll

I don't normally use the cygwin toolset so I can't be sure of my answer... 
I'll look at the code to check. But the above is supposed to be what all win32 
toolsets follow.

I do have one question for you... Are you using the a bjam.exe built for the 
cygwin shell? Or are you using the win32 bjam.exe? They behave differently to 
accommodate the theoretical Unix emulation.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq