Re: [Boost-build] Re-running library tests

Subject: Re: [Boost-build] Re-running library tests
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-03-09 19:18:25

AMDG

On 03/09/2018 12:07 PM, Mateusz Loskot via Boost-build wrote:
> 
> TL;TR: How can I re-run a library test(s) if test source/target are up-to-date?
> 
> It has been a long time since I fiddled with Boost.Build last time
> and I'm re-discovering things, so may be missing something obvious.
> 

I find it easiest to touch the source or use -a (rebuild all).

> I run array tests:
> 
> cd D:\dev\boost\boost\libs\array\test
> b2 -q
> 
> and all tests build and pass.
> I want to run the tests again. but all I get is this:
> 
> b2 -q
> ..\..\..\libs\log\build\Jamfile.v2:45: Unescaped special character in
> argument <define>$(flag)=1
> D:/dev/boost/boost/libs/predef/check/../tools/check\predef.jam:46:
> Unescaped special character in argument $(language)::$(expression)
> Performing configuration checks
> 
>     - default address-model    : 32-bit (cached)
>     - default architecture     : x86 (cached)
>     - symlinks supported       : yes (cached)
>     - BOOST_COMP_GNUC >= 4.3.0 : no  (cached)
> ...patience...
> ...found 2296 targets...
> 
> 
> Refreshing my memory about options:
> 
> b2 --help-options
>   -tx; Rebuild the target 'x', even if it is up-to-date.
> 

Unfortunately -t refers to the internal Jam target name,
and is not very useful for Boost.Build.

In Christ,
Steven Watanabe