On 6/2/2011 1:40 PM, Steven Watanabe wrote:
On 06/02/2011 10:28 AM, Gennadiy Rozental wrote:
Edward Diener<eldiener<at> tropicsoft.com> writes:
Attempting to run regression tests for the 'test' library on the Boost trunk I receive as output:
I've made no changes recently (unless someone else did). Maybe you should redirect this to Boost.Build guys.
The problem is the Jamfile load order caused by this structure:
/ - Jamroot: use-project /boost/test : libs/test/build ;
- libs/test - Jamfile.v2 - build - Jamfile.v2 - test - Jamfile.v2
Running bjam in libs/test/test results in libs/test/build/Jamfile.v2 being loaded before Jamroot is fully loaded. (This is a bug in Boost.Build.)
Will this be fixed in Boost Build ? Is there a workaround to this problem ? I did not notice any other library failing in this way. is it the Test library directory structure which causes this problem in Boost Build, or something else ? As always, Steve, thanks for figuring this out.