From: ColdShine <col...@us...> - 2008-08-30 10:52:21
|
2008/8/30 ColdShine <col...@us...>: > C:\Programs\MinGW\bin\windres.exe: can't open file `XP': No such file > or directory > > So I kept brainstorming, with the hint that --use-temp-file gets rid > of the problem, so it might have to do with subprocesses... maybe > invoked using cmd.exe... so I connected that to the AutoExec script my > cmd.exe runs *every* time it's started, as in: > > HKLM\Software\Microsoft\Command Processor\AutoRun = C:\Programs\Bin\AutoExec.cmd > > Which is mostly for aesthetic reasons, and contains: > > @echo off > cls > title %UserName%@%ComputerName% - Command prompt > ver > > Where ver echoes "Microsoft Windows XP ...". > So I tried deleting the registry value, and... that solved the > problem. windres 2.18 now runs without any problems, and chances are > 2.17 would work too, as the ver echoed line is indeed line 1, so that > could be what it was complaining about. > > Though I do need the modified title in the command prompt, so I'll > restore the AutoExec and try to set an environment variable with > default options for windres to include --use-temp-file or, failing > that, I'll create a .cmd script which lanches windres with that > additional option. Okay, I definitely solved the problem by adding a check in the beginning of AutoExec.cmd: @echo off if defined _ goto :EOF I first had it dump the environment with set > file, then I noticed a var that I seem to remember to be more related to POSIX programs rather than DOS/Windows, $_, so this just checks that the var is not defined; if it is, halts execution of the script. I just rebuilt a test res file without any problems, without any extra command line options for windres. CS |