Re: [Boost-build] Should link=static disable all shared library tests?

Subject: Re: [Boost-build] Should link=static disable all shared library tests?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-01-23 22:11:47

AMDG

On 01/23/2016 07:47 PM, Kuhl, Brian wrote:
> I'm invoking the boost test suite with command similar to the one below:
> 
> source  ./$(VXWORKS_ENV_SH) &&  cd status   &&  \
>                ../b2 -j$(JOBS) --prefix=$(ROOT_DIR) --libdir=$(LIBDIR)/$(TOOL_COMMON_DIR) --includedir=$(VSB_DIR)/usr/h/public   \
>                                  link=static toolset=gcc-vxworks target-os=vxworks testing.launcher=./vxworks_boost_test_run.exp \
>                                 "--limit-tests=atomic|date_time|accumulators|algorithm|align|array|assert"
> 
> Several library tests are failing because of the lack of shared libraries, despite the designation of link=static.
> So far I've encountered tests in system, random and filesystem that insist on trying to link against shared libraries..
> 
> Is this expected behavior for some reason, or a defect that should be corrected?
> Looking at the regression targets I don't see any that would typically use static linking.
> 

  This behavior is expected.  Boost.Random
explicitly runs the same test with both
static and shared libraries.  I assume
it's the same for the others.  In any case,
the target properties override anything specified
on the command line.

In Christ,
Steven Watanabe