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: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-09-10 02:57:18

On 09-Sep-15 10:11 PM, Antony Polukhin wrote:

> In Jamfile I'm explicitly requesting to build shared library:
>
>      lib my_plugin_sum : ../example/tutorial1/my_plugin_sum.cpp :
> <link>shared ;
>      lib my_plugin_aggregator :
> ../example/tutorial2/my_plugin_aggregator.cpp : <link>shared ;
>
> But when I'm feeding those libraries to the test as input files:
>          [ run ../example/tutorial3/tutorial3.cpp : : my_plugin_aggregator
> my_plugin_sum ]
>
> I recieve the following 2 first parameters, one of which is a static
> library:
> "D:\boost\bin.v2\libs\dll\test\msvc-12.0\dbg\adrs-mdl-64\thrd-mlt\my_plugin_sum-vc120-mt-gd-1_60.dll"
> "D:\boost\bin.v2\libs\dll\test\msvc-12.0\dbg\adrs-mdl-64\thrd-mlt\my_plugin_sum-vc120-mt-gd-1_60.lib"
>
> Is there a way to receive only shared libraries via input-files?

Antony,

I would presume your test can look at the first parameter only, and that would be a quick fix for you?

We have pull request for DLLs with no associated lib file, at:

        https://github.com/boostorg/build/pull/28

However, that pull request was adding support for resource-only DLLs, and likely will break plugin DLLs,
and no revised version was submitted so far.

If adjusting test case is not an option, I probably can write you custom code to filter out lib target.

- Volodya