From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2001-11-05 09:09:12
David Abrahams wrote:
>>>Another option maybe is to recreate the whole library if the
>>>changes. Thus the Jamfile should set a dependency on itself.
> Yes, I've been planning all along that all targets would depend on the
> Jamfile which defines them. Systems like cons and scons have a superior
> scheme which encodes the important info (such as which files are members of
> an archive) into an MD5 checksum which gets stored somewhere and compared
> between builds to see if it has changed. That would be nice, but not
> critical, I think.
It's not critical indeed. It would solve to the problem of the OP though
Since a build system can never be wrong, I would suggest that
Boost.Build _or_ has NOARSCAN defined, _or_ has a dependency on the
This way, the build system is never wrong when a source file gets deleted.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk