Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2003-02-14 10:42:09

"Neal D. Becker" <nbecker_at_[hidden]> writes:

> On Friday 14 February 2003 10:25 am, Vladimir Prus wrote:
> [...]
>> > Oh, I see. But this doesn't get installed by any RPM. Should it? What
>> > is the minimum needed to install in order to be able to play with 3rd
>> > party boost packages?
>> I'm afraid that full tree is needed now and I'm not sure what can be done
>> about it now. I think that for Boost.Build V2 will just have a separate rpm
>> which would allow building 3rd party packages. This might be possible
>> with V1, although I'm not sure I have the time (and access to Redhat box
>> ;-) )
> OK, I installed the whole boost src tree as /usr/local/src/boost_1_29_0
> I installed my 3rd party package in my home directory, as ~/program_options.
> Now let's try:
> cd ~/program_options/libs/program_options/build
> BOOST_BUILD_PATH=/usr/local/src/boost_1_29_0 bjam
> ../../../Jamrules: No such file or directory
> ...found 69 targets...
> ...updating 11 targets...
> MkDir1 ../../../libs/program_options/build/bin
> MkDir1 ../../../libs/program_options/build/bin/libprogram_options.a
> MkDir1 ../../../libs/program_options/build/bin/libprogram_options.a/gcc
> MkDir1 ../../../libs/program_options/build/bin/libprogram_options.a/gcc/debug
> MkDir1
> ../../../libs/program_options/build/bin/libprogram_options.a/gcc/debug/runtime-link-dynamic
> gcc-C++-action
> ../../../libs/program_options/build/bin/libprogram_options.a/gcc/debug/runtime-link-dynamic/cmdline.o
> ../src/cmdline.cpp:19:45: boost/program_options/cmdline.hpp: No such file or
> directory
> ../src/cmdline.cpp:20:44: boost/program_options/errors.hpp: No such file or
> directory
> [...]
> Well, that doesn't work. Is it possible to build 3rd party packages like this
> outside the boost tree?

I'm not sure I understand the question, because the answer I'm about
to give is one that I'm sure Volodya already knows:

With the current version of Boost.Build, if you want to use Boost in a
Boost.Build project that's outside the Boost tree, you have to use
<library-path> and <find-library> (which translate into -L... and
-l...) rather than <lib> and <dll>. The latter automatically cause
dependencies to be rebuilt when outdated; in the former case you'll
have to make sure that whatever Boost library objects you're dependent
on are explicitly built first.


Dave Abrahams
Boost Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at