Using a part of a Jamfile.v2
I was thinking about tweaking a library in Boost. Its BOOST_ROOT/libs/math/test/ directory is shared with some other libraries, so there's a lot of test files and the shared Jamfile.v2 used to make the tests is huge. Is there a way to restrict which targets are built from the command line? Right now, it takes MANY hours to go through every test. (When I did something similar last week with another library, I just commented out all the other libraries sharing the file. Do I have to resort to that all the time?) Daryle W.
AMDG On 02/21/2012 11:18 AM, Daryle Walker wrote:
I was thinking about tweaking a library in Boost. Its BOOST_ROOT/libs/math/test/ directory is shared with some other libraries, so there's a lot of test files and the shared Jamfile.v2 used to make the tests is huge. Is there a way to restrict which targets are built from the command line? Right now, it takes MANY hours to go through every test. (When I did something similar last week with another library, I just commented out all the other libraries sharing the file. Do I have to resort to that all the time?)
Just put the name of the test on the command line. For example, Jamfile.v2: run test1.cpp ; run test2.cpp ;
bjam test1
In Christ, Steven Watanabe
participants (2)
-
Daryle Walker -
Steven Watanabe