Re: [Boost-build] Question re building libraries

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-10 03:26:19

On Tuesday 28 February 2006 13:04, MANSION, James, FM wrote:

> >I'm not sure about flags for a.cpp. On Linux, the above won't
> > add -fPIC, but this is inefficiency, not a show-stopper. On
>
> Windows -- what flags specifically should be there?
>
> I would regard this as a show-stopper.  Some libraries need to
> Be compiled with knowledge that they are in a DLL - ACE,
> wxWidgets come to mind.  Some MFC stuff does as well.

But it's much less common to build ACE or wxWidget as static lib and then link 
it into DLL.

> Its not generic but specific to the code at hand.
>
> As I see it, a static link library is a way to manage a bunch
> of objects conveniently as a whole such that the link editor
> can select from it to fulfill requirements.  DLLs are more
> like executables than static libraries.
>
> So ... The compilation switches that need to be applied to a
> source file to create an object should really relate to
> whether it will eventually be directly linked into an executable,
> or linked into a DLL.  It should not be determined by whether it
> gets aggregated into a static library as an intermediate step.

This can be done by creating new property <shared-linkable>, that control if 
the object file will eventually end up in a shared library.

Can you file enhancement request on

   https://zigzag.cs.msu.su/boost.build

?

Thanks,
Volodya