RE: windres bug in -I/--input-dir option

[Anthony Penniston]

Okay Nick, I've gone ahead and reported it here:
http://sourceware.org/bugzilla/show_bug.cgi?id=11711
(added you to the CC list - I hope you don't mind.)

I note there that if backwards-compatibility is necessary, then at least
 "--include-dir=res" can behave as expected. I agree, it's barely noteworthy; 
but if you have a patch on the ready, we may as well take the opportunity to 
make good software better.

Cheers.
Anthony

p.s. would be nice if GCC and binutils bugzilla user accounts were merged, so 
only one registration is needed.

----------------------------------------
> Date: Wed, 16 Jun 2010 15:50:12 +0100
> From: address@hidden
> To: address@hidden
> CC: address@hidden
> Subject: Re: windres bug in -I/--input-dir option
>
> Hi Anthony,
>
>> If you specify "res" as an include directory via the "-I"
>> or "--include-dir=" options, windres mistakenly assumes
>> this to be the output format (and issues a warning saying
>> to use "-J" instead). The workaround if you have such an
>> input directory named "res" is to specify it as "./res",
>> though this really shouldn't be necessary.
>
> I am not sure if this important enough to be worth fixing. Especially
> there is a simple workaround as you have mentioned. I have a patch that
> will correct the behaviour (attached) but it has the potential to
> confuse users used to the old, deprecated, behaviour. If you really
> feel that this feature needs to be corrected in the sources please open
> a bug report on the binutils bugzilla system and I will make the patch
> official:
>
> http://sourceware.org/bugzilla
>
> Cheers
> Nick Clifton
>
>
>
                                          
_________________________________________________________________
Game on: Challenge friends to great games on Messenger
http://go.microsoft.com/?linkid=9734387