Re: [Boost-build] question regarding building with bjam v2

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-07-17 13:39:37

Robert Ramey wrote:

> Thanks for getting back to me so quickly.
> 
> I'm still looking into this.
> 
> It turns out that my Jamfile.v2 contains:
> 
> <link>shared:<define>BOOST_SERIALIZATION_DYN_LINK=1
> 
> Which turns out to the the "magic" which is provoking the behavior.
> I would guess then that I'm building libraries for DLL while boost/test
> is perhaps building/testing a static library so this issue doesn't appear.

I would expect the testing process to be building shared libraries, too,
as it's the default in Boost.Build V2. You might try to run bjam in
libs/serialization/test directory to see if that works.

> I don't remember why that line was included in the original Jamfile.  
> I did have a lot off difficulty with auto-link because I had one library
> wserialization which exports and API but at the same time imports
> and API from another library - serialization.  Perhaps that's why
> I included that.

I'm not sure I understand what problems will arise from that arrangement.
It seems there are separate defines:

        BOOST_SERIALIZATION_DYN_LINK=1
        BOOST_WSERIALIZATION_DYN_LINK=1

so everything should be OK.

> So I'll just plug away a while longer.
> 
> But I do have a question:If the Jamfile.v2 in the boost root contains
> <define>BOOST_ALL_NO_LIB=1 does this mean that for users
> the default is auto-linking turned off?  Is that correct?

No, it only means that 'exe' projects under Jamfile.v2 won't use autolinking.
That define does not affect libraries.

- Volodya