From: Mat Marcus (blazer_at_[hidden])
Date: 2005-06-15 11:14:40
On 6/15/05, Vladimir Prus <ghost_at_[hidden]> wrote:
> On Monday 13 June 2005 23:43, JOAQUIN LOPEZ MU?Z wrote:
> > For the record, the same thing happens with BB2 in vacpp.
> > For instance, serialization builds into:
> > boost_serialization-xlc-d-1_33.so.1.33.0
> And what's wrong with that? I think it's exactly the same as in V1.
We have a library that depends on boost. We've been building some of
the required boost libs using the alias rule. Using BBv2 from 1.32.0
this yielded boost libraries without any version suffix. We were then
able to provide clients of our library with IDE-based project
stationery that links against the BBv2-built artifacts. Everything
worked fine. But, when we upgraded to CVS BBv2, the BBv2-built boost
libraries now have a 1.33.0 suffix. As a result, they are no longer
usable by the IDE-based client projects.
This change has cost us a fair amount of time so far. First we had to
figure out why, after upgrading and cleaning, our IDE-based client
projects were breaking. Second we had to try to determine whether this
was intentional BBv2 behavior or a bug. Since we couldn't find any
documentation about the change we posted here and waited. Third we
(still) have to figure out a new Jamfile structure to support our
desired workflow. It would be great to have some guidance on this last
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