From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-26 12:15:06
----- Original Message -----
From: "Steven Knight" <knight_at_[hidden]>
> Vladimir wrote:
> > and you can't predict an
> > content of a binary file.
> But you *can* process the content and look for a specific string
> that suggests it was built correctly. Or, if it's a program you
> you can execute it to see that it worked correctly.
In general I hope that our build system /framework/ tests will not be
dependent on doing much of anything with binary files. I would like to
localize all of that in tests for individual toolsets and target
platforms. Any individual tester probably doesn't have all the toolsets
and platforms at his disposal; especially not within a single test run.
It should be possible to pass "all" tests anyway. That's why I favor
doing most of the testing with dummy toolset/platform specifications
that operate portably in terms of simple text files.
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