From: bill_kempf (williamkempf_at_[hidden])
Date: 2002-08-21 10:56:40
--- In jamboost_at_y..., "David Abrahams" <dave_at_b...> wrote:
> Hi Bill,
> I just checked in some changes to your Jamfile which should correct
> Please try a clean rebuild.
OK, everything compiles, but nothing runs! This is now true no
matter what TOOLS I use!
> The unit-test rule is really not very sophisticated: it makes
> target dependent on a successful run. Of course that means that it
> removed if the run fails.
Which is precisely what I want. :( The run rule will run the
executable (or it should, AFAIK, though the Jamfile you checked in
fails to run the executables for any variants using any tool set)
every single time. This will make it difficult to use the tests in
this directory for finding and fixing problems since they build 4
variants per test X 4 toolsets (I'm running msvc, vc7, borland, gcc)
X 6 tests = 96 runs on every invocation.
> It also means that when I set the JAMSHELL
> variable on the .exe so that it gets linked through spawn instead
of a .bat
> file to work around NT line length problems, it also gets run
> spawn, which fails (since the command includes environment
I don't understand why this is a problem only with the gcc toolset.
The msvc, vc7 and borland toolsets all work flawlessly with unit-
test, and they should all be doing the same thing in this case, no?
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