Re: [Mingw-users] windres unavoidably reports syntax error at *.rc:1

[ColdShine <col...@us...>]

2008/8/29 Keith Marshall <kei...@us...>:
> On Friday 29 August 2008 22:18:32 ColdShine wrote:
>> Actually I realize now I forgot to mention something:
>>
>> C:\Profiles\ColdShine>windres -V
>> GNU windres 2.17.50 20060824
>>
>> So apparently I'm working on a slightly newer version.
>
> That could very well be the broken one I referred to in my earlier
> post; you should definitely try a different version.

Well... I tried the latest I could find, 2.18. I did a manual
installation, untar'ing the packages the automated installer
downloaded for me, but replacing the binutils-2.17 with binutils-2.18.
This is the result of the same test:

C:\Profiles\ColdShine\Projects>windres -V
GNU windres (GNU Binutils) 2.18.50.20080109

C:\Profiles\ColdShine\Projects>windres -v -i empty.rc -o empty.res
Using `gcc -E -xc -DRC_INVOKED  empty.rc'
Using popen to read preprocessor output
windres: can't open file `XP': No such file or directory
empty.rc:0: fatal error: when writing output to : Invalid argument
compilation terminated.
windres: preprocessing failed.

So apparently now I have a different yet completely random error
message, complaining about something that doesn't even exist in the
preprocessed rc file:

C:\Profiles\ColdShine\Projects>gcc -E -xc -DRC_INVOKED  empty.rc
# 1 "empty.rc"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "empty.rc"

This is driving me completely insane.

Just to make sure the 'XP' string isn't picked from some environment
variable, I run this in the same console window:

C:\Profiles\ColdShine\Projects>set | grep XP

It didn't return anything.


By the way, yesterday I even wrote a CMD file which just echoes the rc
file to stdout, and told windres to use that one as a preprocessor,
just to make sure gcc is completely innocent. As expected, windres
still complained.

I guess I'm gonna try every version of windres I can find.

Thank you again.
CS