|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-08-15 14:33:37
On Sunday 12 August 2007 09:37:04 Robert Ramey wrote:
> Vladimir Prus wrote:
> > Robert Ramey wrote:
> >
> >> I've recently running all the boost tests in order to test my library
> >> status facilty before checking it in. In the course of doing this
> >> I've noticed that
> >> in a couple of cases, bjam doesn't create the proper test directory.
> >> Here are the tests:
> >>
> >> a) program_options/test/conver
> >
> > Note that a target by this name does not exist. There's 'test_convert'
> > target though. That target is 'exe' target, so it's not a 'test',
> > formally speaking, therefore no 'test name' is expected in the target
> > path.
>
> I get a directory
> bin.v2/libs/program_options/test/msvc-7.1/debug/link-static/threading-multi
>
> note the absence of test_convert.test.
As I said, "test_convert.test" is not supposed to be prevent in this case.
> My reading of process_jam_log.cpp suggests that this is not expected. The
> test-name is
> determined to be blank. Is this OK and should I just ignore it? or should
> something be done about it. I'm not sure what the point would be if the
> results are generated without a corresponding test name. I wonder if in
> fact this is what the authors of the Jamfile.v2 intended or it is an
> oversight that should be addressed.
For program_options, the target in question is not even supposed to
be automatically run, and should not be reported.
- Volodya
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk