Re: [v2] Overuse of response files?

From: David Abrahams (dave_at_[hidden])
Date: 2005-05-24 11:13:37

Vladimir Prus <ghost_at_[hidden]> writes:

> On Wednesday 18 May 2005 06:33, David Abrahams wrote:
>> David Abrahams <dave_at_[hidden]> writes:
>> > Vladimir Prus <ghost_at_[hidden]> writes:
>> >> I attach a prototype implementation that implements this idea for
>> >> msvc.compile.c++ action, and would appreciate if you try it.
>> >
>> > Doesn't work at all. Did you test it? It creates circular
>> > dependencies, among other things. The enclosed works... sort of.
>> >
>> > It's really inconvenient and IMO senseless to use response files for
>> > compiles of single source files. The only purpose is to shorten
>> > command lines, and when the response file name is likely to be as long
>> > as the input file name you don't gain anything.
>>
>> By way of clarification, I say this is inconvenient because: suppose I
>> preprocess the file successfully into another file, and I want to
>> substitute it on the command line. In this case I have to find the
>> response file and edit it.
>
> Ahm... so you want *filename only* to be kept on command line. That sounds 
> reasonable, and I now understand your argument about:
>
> The only purpose is to shorten
> command lines, and when the response file name is likely to be as long
> as the input file name you don't gain anything.
>
> I'll see if this can be done.

That could still push the line length limits a bit, since now you'll
have the .rsp and the source file name together.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com