From: David Abrahams (dave_at_[hidden])
Date: 2005-10-23 10:15:17
Reece Dunn <msclrhd_at_[hidden]> writes:
> David Abrahams wrote:
>> That's a little ugly. You get a compilation error; you want to
>> diagnose it. Then you have to rebuild with --show-response-files,
>> copy the response file contents and the rest of the command line,
>> replace -c with -E, and invoke the compiler again to preprocess.
> You only need to rebuild if we go for option .
> Option  (see also my [BBv2] response files - behaviour change
> (and solution!) thread for details) will print the response file
> content along with the command line on failure.
> Alternatively, you can copy/rename the response file on failure to
> keep it around, while allowing the response file target to be
> regenerated properly and preventing problems with the above.
It's not bad -- better than nothing for sure -- but the command line
as it appears will refer to the wrong file if you want to retry the
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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