minral you are not going to like what I have to say. There are reasons why wine is failing and none of them are friendly.
Windows programs expects either ANSI or UTF16 on stdout and stderr then Linux programs go and output UTF8. This is the disconnect.
Yes there are ways to work around this issue. Using
add the installation directory to PATH (z:\opt\altera\10.1sp1\quartus\bin)
add '.' to PATHEXT
both are fairly much the wrong way. The correct way is a true pain even the hack way is a true pain.
The correct way are .exe.so files calling the correct programs wrapping the output and convert application outputs into windows format. In other words horible.
The horrible is create shell scripts and using a unix name pipe files.
Line above makes a unix named pipe file.
Code: Select all
#!/bin/bash
echo $@
function slow {
echo second $@
echo hi
sleep 10s
echo hi
}
slow $@ >testpipe
This code is something to run slow mess.exe this example
mess.cmd is this file. Now the trick here is the Linux programs sends all it output to testpipe file type will print out everything in test until program filling it disconnects. But do remember the data coming out of testpipe is UTF8 not what windows programs should see so might pay to redirect that to NULL/log file.
There is a real need for something like native.exe.so. Failures happen when Linux programs just run in back ground also failures use to happen when Linux programs would feed UTF8 into Windows programs.
This horible will only allow a single instance as well.
