From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-12-10 04:01:35
On Sunday 09 December 2007 18:35:08 Martin Wille wrote:
> Vladimir Prus wrote:
> > I had just got a totally crazy idea -- we have some algorithms
> > to compute target paths, and --abbreviate-paths options, and it
> > not quite good yet.
> > How about just using MD5 or SHA-1 of build properties to form
> > target path? Might sound scary, but after working with git for
> > a bit, I find that using SHA-1 to identify things is not so
> > bad, as copy-paste works. To make things easier, we might
> > put a file in each build directory that lists all the properties
> > of the files in that directory.
> > Comments?
> This requires that there is some additional support for exteneral tools
> that are supposed to operate on the directory tree created by BB.
> As a simple example: "Please, remove everything for Library X and
> Toolset Y built for use in shared libraries".
I think several tricks might work:
1. In each build directory, place a file with the list of properties.
2. Add --show option to Boost.Build, that lists what files, with
what properties, will be put to what directory.
3. Generate a single "manifest" file, that tells for each hashed directory
name the properties -- like (1) but with a single file.
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