From: Robert Ramey (ramey_at_[hidden])
Date: 2007-07-17 13:10:54
Thanks for getting back to me so quickly.
I'm still looking into this.
It turns out that my Jamfile.v2 contains:
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 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.
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?
"Vladimir Prus" <ghost_at_[hidden]> wrote in message
> Robert Ramey wrote:
>> I've checked out the latest version of Boost 1.34 - tagged
>> I've carefully read the Boost Build documentation (very much improved)
>> attempted to build the serialization library with the command line
>> executed in the directory ../libs/serialization/build:
>> bjam --toolset=msvc-7.1
>> I get compilation errors - which I've never seen before.
> I never seen those error, either -- in particular because
> you did not post them.
>> /Gy -c
>> Which seems almost OK. It looks like my compilation errors are related
>> someway to the switch
> Related in what what?
>> I've looked at the Jamfile.v2 for boost serialization build and it
>> includes only -DBOOST_SERIALIZATION_DYN_LINK=1
>> Searching around, I find in the boost root directory Jamfile.v2 which
>> contains the following:
>> # disable auto-linking for all targets here,
>> # primarily because it caused troubles with V2
>> Which seems that it might be relevant to my case - it begs for a better
> Ehm, long time ago the library names produced by V2 had no relation
> to the library names autolinking expected. It was fixed since
> However, it does not seem to be any point in enabling autolinking
> for testing, so it's disabled.
>> Soooooooo - what do I do now? The following facts are also interesting:
>> a) the official boost test results are all passing for this combination
>> compiler and library. They don't show any compilation errors. The
>> matrix doesn't let me see the compilation command line for the build - I
>> would be curious to see it.
> I'm sure BOOST_ALL_NO_LIB is present.
> - Volodya
> Unsubscribe & other changes:
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