|
Boost : |
From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-03-30 22:43:40
Benjamin Kosnik wrote:
> When I build boost-1.31.0, like so:
>
> bjam -sPYTHON_ROOT=/usr -sPYTHON_VERSION=2.2 -sTOOLS=gcc -sBUILD=release --prefix=/usr
>
> I end up with a bunch of oddly-named library files:
>
> libboost_filesystem-gcc-1_31.a
> libboost_filesystem-gcc-1_31.so.1.31.0*
> libboost_filesystem-gcc.a
> libboost_filesystem-gcc.so*
>
> is there a way to run bjam or configure the build process so I get something sensible, like:
>
> libboost_filesystem.a
> libboost_filesystem.so.1.31.0
> libboost_filesystem.so (symlink)
Not with the current build procedure. This is intentional as we can't rely on,
or assume, that the user has only one compiler in use. Or that they only want
a specific variant, threading, runtime, etc. The hope is that system packagers
provide for that.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk