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

From: bill_kempf (williamkempf_at_[hidden])
Date: 2002-08-21 17:26:08

--- In jamboost_at_y..., "David Abrahams" <dave_at_b...> wrote:
> From: "bill_kempf" <williamkempf_at_h...>
> > Not precisely. It only cleans up files/directories that it 
creates
> > and thinks should be cleaned. If any files are left over the
> > directories aren't removed.
> 
> You're right. "clean" is failing to remove some of the testing 
residue
> files. I just fixed that, I think.

I just did a cvs update and still see the same results. Did you 
check the fix in?

> > It would be nice to have a distclean
> > that clobbered the directory no matter what.
> 
> Wouldn't it?
> 
> > Further, and this is the one I often find frustrating, clean also
> > invokes clean on dependent projects. So cleaning
> > $BOOST/libs/thread/test will also clean $BOOST/libs/thread/build 
and
> > $BOOST/libs/test/build. It would be nice to have a target that 
only
> > cleaned the current project, leaving dependent targets alone.
> 
> Sure would!

Any chance these are in the plans for V2? Please? ;)

> > bjam -sTOOLS=vc7 clean
> > bjam -sTOOLS=vc7 test
> >
> > Produces the following tree:
> >
> > bin
> > test_base.test
> > debug
> > runtime-link-dynamic
> > threading-multi
> > runtime-link-static
> > threading-multi
> > release
> > runtime-link-dynamic
> > threading-multi
> > runtime-link-static
> > threading-multi
> >
> > Since I specified only one target, "test", it makes sense that 
only
> > one was built.
> 
> No it doesn't. "test" is an abstract target like "all" or "exe", 
which
> depends on a whole bunch of actual targets, namely all of the test 
results.

OK, that makes sense. But does this mean there's no way to specify 
only certain tests be added/run from the command line? For 
instance, let's say I just want to run test_condition.cpp.

> I've enclosed a listing of the commands executed when I build 
test, then
> clean, then test again.

Enclosed it where?

> I can't understand why it wouldn't be happening for
> you, but you could look at the -d+12 output to see what decisions 
it's
> making.

I'll do that and let you know if I find anything.

> > What's not as obvious is why the target produced
> > is "test_base.test", why the target for test_thread.cpp is this
> > target, or what target name would be valid for, say, the target 
that
> > builds test_condition.cpp. Seems like a case where I should 
RTFM,
> > but it doesn't appear that the "run" target is documented.
> 
> It's documented in tools/buid/testing.jam only.

OK, I've looked there, and the documentation is minimal. To really 
understand everything that's going on you have to read the Jam code, 
which I can only half follow. Any chance anyone could work on 
documenting these target types in the bjam documentation?

Bill Kempf