Subject: Re: [Boost-build] Better caching of configure checks
From: John Maddock (boost.regex_at_[hidden])
Date: 2012-10-16 03:51:52
>I've already adjusted the regular configure output
>to indicate which checks are cached. e.g.
> - long double support : yes (cached)
>Hopefully, this is enough to prevent surprises.
>I'll definitely document the details of the behavior
>in the Boost.Build docs as well.
That helps a lot. It would be even better if at the start of the configure
checks the output could read something like:
Running configuration checks
Some cached configure checks were found, run with --reconfigure to force
these to be rebuilt.
Then we don't have to go hunting around in docs for the command line option,
and folks that haven't seen this discussion won't be out in the cold.
Just my 2c worth, John.
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