I am writing about a known issue that
is not very well documented. I just
tried OSDK under wine. More
specifically I tried to compile the c
version of the hello_world_simple. The
compilation was unsuccessful giving
error messages like:
Couldn't open output file!
ERROR : Build failed.
Later, I found that the solution was to
create a folder named "build" inside
project path.
Reading the comments in the make.bat I
realised that this is a known bug.
I would suggest, until this bug is
fixed, to print a hint in the error
messages like "... if you are running
OSDK under wine then create a folder
named build in your project path and
try again..."
V.
Written from my Oric, please allow for
typos and misspells.
OSDK in wine and "build" folder
I guess I need to spend a bit of time on trying to fix that more elegantly.
I remember I had the problem, I don't remember what was actually the cause - the fact that wine's command interpreter is not 100% compatible with Windows's one is part of the problem.
If somebody can find how I can detect I'm running under Wine in a batch file, it may be possible to add a specific code path for that.
I remember I had the problem, I don't remember what was actually the cause - the fact that wine's command interpreter is not 100% compatible with Windows's one is part of the problem.
If somebody can find how I can detect I'm running under Wine in a batch file, it may be possible to add a specific code path for that.
-
- Flying Officer
- Posts: 148
- Joined: Fri Oct 12, 2007 8:08 pm
Well, last time I checked the batch files I first created on Windows 95 were still running fine on Windows 7. The fact is that WINE's command line interpreter does not do everything exactly like what Windows's does. Most standard commands works the same, but when you start playing with redirections, side effects, formatting, etc... then things start to break appart.
Typically this does not behave the same:
I guess I could just always create the folder and redirect the error message somewhere invisible...
Typically this does not behave the same:
Code: Select all
::
:: Create a build directory if it does not exist
:: Mike: Seems to fail creating the folder under Wine, resulting in a failed build
:: Mike: What about testing for BUILD\. instead ?
::
IF EXIST BUILD\NUL GOTO NoBuild
MD BUILD
:NoBuild
-
- Flying Officer
- Posts: 148
- Joined: Fri Oct 12, 2007 8:08 pm