hardcode-dll-path, Unit-Test Pseudotarget?

From: peter_schoen1_web_de (Peter.Schoen1_at_[hidden])
Date: 2003-08-05 11:20:02

Hi,

I am currently learning boost.Build and have a few questions:

1. I tried to get boost.Build to hardcode (-rpath) a prebuilt lib 
into an executable:

lib boost-unit-test
:
: <name>boost_unit_test_framework
<search>/somePath/threading-single
:
: <include>/somePath/boost_1_30_0
<dll-path>/somePath/threading-single
<library-path>/somePath/threading-single
;

I noticed that both <search> as well as <library-path> add a "-L" flag
to the linker's command line. What's the difference between the two?

<dll-path> seems to trigger the -rpath option. If dll-path is not set,
but <library-path> is set, no -rpath option is generated. Is that 
intended?

2. Is there a global pseudotarget that I can use in order to run all
the unit tests in a project tree? "bjam test" or "bjam tests" didn't 
work.

Many thanks & very best wishes

-Peter-