Re: [boost] bjam in lib/<x>/test is equivalent to run.py

Subject: Re: [boost] bjam in lib/<x>/test is equivalent to run.py
From: Jim Bell (Jim_at_[hidden])
Date: 2010-11-05 11:32:56

On 1:59 PM, Rene Rivera wrote:
> On 11/4/2010 12:31 PM, Jim Bell wrote:
>> To make your own script to rebuild/rerun a particular test, run bjam
>> with -d+2 (i.e., -d2) and direct the output to a file. Then copy the
>> compile&  link commands out of that file.
>
> Or you could just run: cd libs/<x>/test ; bjam -a <name-of-the-test>
> Doing a "bjam -h" or "bjam --help" will point to other useful switches.
>

Let's say you're troubleshooting a thread library problem that only
shows itself during an asio test.

Can you make changes to a thread file (e.g,
libs/thread/src/win32/thread.cpp), then re-run bjam in libs/asio/test
with the appropriate -a flag, and have your thread change be picked up?
I.e, boost thread library rebuilt, app rebuilt, app re-run.