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

4 Sep 2015

      2015-09-04 21:33 GMT+03:00 Rene Rivera :
...
...
2015-09-04 20:38 GMT+03:00 Steven Watanabe :
...
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
 ;
They aren't linked. They are passed in as extra args. Re:
rule run ( sources + : args * : input-files * : requirements * :
target-name ? :
    default-build * )
It's the "input-files" argument.
Thanks, this works. But unfortunately this method requires tests and
examples to be rewritten. Also, is there a way to receive library name
without a version ("libtest_library.so" instead of
"libtest_library.so.1.59.0")?

Solution with TEST_DIR seems friendlier to me. Could it be fixed somehow?

-- 
Best regards,
Antony Polukhin