Re: [jamboost] Re: Fw: [boost] Boost.Build problem?

From: David Abrahams (dave_at_[hidden])
Date: 2002-08-22 11:10:02

From: "bill_kempf" <williamkempf_at_[hidden]>

> That helps to figure out what may be going on. Here's what I see
> when I try that.
>
> bjam -sTOOLS=vc7 clean
> bjam -sTOOLS=vc7 test_thread
> Build output you'd expect, though the target is test_base.test
> bjam -sTOOLS=vc7 test_condition
> C:\home\boost\libs\thread\test>bjam -sTOOLS=vc7 test_condition
> ...found 556 targets...
> ...using 4 temp targets...
> ...updating 4 targets...
> ...using <libs!thread!test\test_base.test\vc7\debug\runtime-link-
> static\threadin
> g-multi>test_base.run...
> succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
> \debug\runti
> me-link-static\threading-multi\test_base.test
> ...using <libs!thread!test\test_base.test\vc7\debug\runtime-link-
> dynamic\threadi
> ng-multi>test_base.run...
> succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
> \debug\runti
> me-link-dynamic\threading-multi\test_base.test
> ...using <libs!thread!test\test_base.test\vc7\release\runtime-link-
> static\thread
> ing-multi>test_base.run...
> succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
> \release\run
> time-link-static\threading-multi\test_base.test
> ...using <libs!thread!test\test_base.test\vc7\release\runtime-link-
> dynamic\threa
> ding-multi>test_base.run...
> succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
> \release\run
> time-link-dynamic\threading-multi\test_base.test
> ...updated 4 targets...
>
> Note that it uses the exact same output directory (i.e.
> test_base.test) and thus nothing happens.

!!!!!!!

> > However, there's clearly a bug somewhere in the interaction of the
> test
> > tools with the <template> feature. The issue is that declare-local-
> target
> > is supposed to return the list of the target files for the target
> it
> > builds. However it appears to be returning results of the form
> > (<some-grist>test_base.test)*, where test_base is the name of a
> template.
>
> Yes, that does appear to be the case.

This bug seems to be the cause of your problems at the top.

Rene, could you please fix this? I don't know why it's happening, but
declare-local-target is returning the wrong thing when <template>
dependencies are used. In fairness, there was a comment describing the
return semantics missing, but I've added it. I'd do this myself, but I
don't know how the <template> stuff works...

Thanks,
Dave