Re: [boost] Critical. Help required. Boost.DLL Jamfile breaks testing with multiple toolsets

Subject: Re: [boost] Critical. Help required. Boost.DLL Jamfile breaks testing with multiple toolsets
From: Antony Polukhin (antoshkka_at_[hidden])
Date: 2015-09-04 14:22:24

2015-09-04 20:38 GMT+03:00 Steven Watanabe <watanabesj_at_[hidden]>:

> AMDG
>
> On 09/04/2015 11:12 AM, Antony Polukhin wrote:
> >
> > There's a big problem with Boost.DLL's Jamfile which I do not know how to
> > fix.
> >
> > Introduction
> > Tests of Boost.DLL create multiple *.so files and install them to a
> > specified TEST_DIR path. Tests consume that TEST_DIR path and search for
> > *.so in there:
> >
> > path-constant TEST_DIR : $(BOOST_ROOT)/bin.v2/libs/dll/test ;
> >
>
> Don't do this.  In addition to the problem
> that you're having, this effectively
> overrides a command line build-dir option.
>
> Instead of passing the directory, you
> should pass the targets, like this:
>
> run shared_library_load_test.cpp
>  : # args
>  : getting_started_libary test_library
>  ;
>

Library *must not* be linked to the test. Those are not actually libraries,
those are plugins, that must be searched by test and loaded using the
Boost.DLL.

-- 
Best regards,
Antony Polukhin