|
Boost-Build : |
From: Andrei Melnikov (andy.melnikov_at_[hidden])
Date: 2006-08-17 16:56:19
On 17/08/06, David Abrahams <dave_at_[hidden]> wrote:
> "Andrei Melnikov" <andy.melnikov_at_[hidden]> writes:
>
> > The rationale of putting all switches to response files was to enhance
> > debugging, not to make it worse.
>
> It makes it worse when you have access to the command-lines, but not
> the files.
But the previous situation wasn't perfect either - you didn't have
access to include paths because they were inside .rsp files.
> > Some switches were inside the rsp files, some switches were on command
> > lines. So I had to look in two different places to find the problem.
> > Now all switches are in a single place.
>
> Great for you if you're not looking at the online build logs to figure
> out what happens.
See below
>
> > If we still want to use -d switch to trace the actual command lines, I
> > think it's a good idea to display the parameters for :E variable
> > modifier at higher debug levels.
> >
> > What do you think?
>
> I don't know what -d and :E do.
:E is used to create .rsp files. And -d is used to specify the debug
logging level.
So I just want to print the contents of RSP files to the debug logs at
certain detalization levels.
-- Andrei
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