|
|
Boost Testing : |
From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2005-06-17 03:19:44
Beman Dawes writes:
> "Aleksey Gurtovoy" <agurtovoy_at_[hidden]> wrote in message
> news:m1k6kwzgx2.fsf_at_tulip.office.meta...
>> Beman Dawes writes:
>>...
>>> and only on one simple test. Say config_info.
>>
>> Unless it's possible to specify this through bjam command line, I'm
>> afraid this part is not that simple to achieve. Of course, what you
>> can always do is to temporary comment out everything but config tests
>> from "status/Jamfile".
>
>>From the bjam command line, you would just say:
>
> bjam ... config_info
>
> That will cause only the config_info target to be run.
>
> The problem with regression.py --bjam-options is that it doesn't place them
> last on the bjam command line. For example:
>
> python regression.py test ... --bjam-options=config_info
>
> produced:
>
> bjam.exe ... config_info "-sALL_LOCATE_TARGET=D:\boost-auto-regr\results"
>
> That doesn't work because config_info has to be the last command line entry
> (not counting the 1>> and 2>&1 redirection).
According to Dave this shouldn't be the case anymore --
http://article.gmane.org/gmane.comp.lib.boost.testing/1467. Let us
know if something still prevents you from doing what you want.
-- Aleksey Gurtovoy MetaCommunications Engineering