Re: [boost] library build confusion

From: David Abrahams (dave_at_[hidden])
Date: 2002-10-15 10:43:50

Rene Rivera <grafik666_at_[hidden]> writes:

> [2002-10-15] David Abrahams wrote:
> 
> >nbecker_at_[hidden] (Neal D. Becker) writes:
> >
> >> I just grabbed boost_1_29_0 and built the libs using:
> >> 
> >> PYTHON_ROOT=/usr bjam "-sTOOLS=gcc"
> >> 
> >> On Linux RedHat8.0.
> >> 
> >> It succeeded, but there is some confusion.  First, the various library
> >> builds are inconsistent with each other.
> >> 
> >> python builds shared libs, both debug and regular.
> >> 
> >> Under
> >> 
> >libs/python/build/bin/libboost_python.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/:
> >> 
> >> 
> >> libboost_python_debug.so.1.29.0
> >> libboost_python.so.1.29.0
> >
> >
> >Really? these should be staged in libs/python/build/bin-stage.  I'm
> >particularly surprised about the latter showing up in the path you
                                    ^^^^^^
> >describe.
> 
> This is actually correct. The "libboost_python_debug.so.1.29.0" is the
> relinked version for staging. That was the only way to get the stage to
> correctly link the names. And that's the one it copies to the stage.

Oh, I think I see. The latter one is the regular build. So why is
stage copying anything at all? Why not just link the target directly
into the stage directory?

-- 
           David Abrahams * Boost Consulting
dave_at_[hidden] * http://www.boost-consulting.com