OSDK in wine and "build" folder

Questions, bug reports, features requests, ... about the Oric Software Development Kit. Please indicate clearly in the title the related element (OSDK for generic questions, PictConv, FilePack, XA, Euphoric, etc...) to make it easy to locate messages.

Post Reply
vrozos
Officer Cadet
Posts: 63
Joined: Mon Nov 21, 2011 12:36 pm
Location: Athens, Greece
Contact:

OSDK in wine and "build" folder

Post by vrozos » Mon Jan 02, 2012 12:12 pm

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.

User avatar
Dbug
Site Admin
Posts: 2366
Joined: Fri Jan 06, 2006 10:00 pm
Location: Oslo, Norway
Contact:

Post by Dbug » Wed Jan 04, 2012 8:27 pm

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.

highwayman
Flying Officer
Posts: 148
Joined: Fri Oct 12, 2007 8:08 pm

Post by highwayman » Thu Jan 05, 2012 9:31 pm

windows is not compatable with windows - it's just a marketing name for a long line of products.

go into the wine config & try changing the windows type.

User avatar
Dbug
Site Admin
Posts: 2366
Joined: Fri Jan 06, 2006 10:00 pm
Location: Oslo, Norway
Contact:

Post by Dbug » Thu Jan 05, 2012 10:05 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:

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
I guess I could just always create the folder and redirect the error message somewhere invisible...

highwayman
Flying Officer
Posts: 148
Joined: Fri Oct 12, 2007 8:08 pm

Post by highwayman » Mon Jan 09, 2012 12:21 am

i can see right away that one issue would be mixing upper & lower case in the name.

windows is not case sensitive - Linux is.
wine cant change that aspect becuase it could cause more problems than it could solve.

slashes are reversed too - paths may not be translated correctly.

User avatar
Dbug
Site Admin
Posts: 2366
Joined: Fri Jan 06, 2006 10:00 pm
Location: Oslo, Norway
Contact:

Post by Dbug » Mon Jan 09, 2012 7:13 pm

In this particular case the folder is always called BUILD, so this should really not cause any issue :)

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests