May we use winelib-wcmd as $COMSPEC command processor?

[Alexandre Julliard]

Uwe Bonnes <bon at elektron.ikp.physik.tu-darmstadt.de> writes:

> It works with a winelib executable, when COMSPEC points to the real file. As
> our present built system creates .exe.so files, comspec must specify this
> existing .exe.so file (or the .exe.so file must be renamed to an .exe
> file). Just as a reference for others...

You shouldn't need to rename the file or point to the .exe.so. Unless
you have changed the loadorder, a .exe loaded from the system
directory should match the .exe.so, just like it does for dlls
even if the file itself doesn't exist.

So a CreateProcess of %systemdir%\wcmd.exe should launch wcmd.exe.so,
just like a LoadLibrary of %systemdir%\user32.dll will load
user32.dll.so, even if you don't have a real user32.dll file in
there. If it doesn't do this there's a bug somewhere.

-- 
Alexandre Julliard
julliard at winehq.com