Note: Detailed informations on how to use the OSDK with a Linux operating system using Wine are given at the end of the page.
The only important thing you need to do is to set an environment variable to locate the OSDK folder. Starting from this points the make file is able to locate the other files by itself.
If you install the OSDK on your drive C:\ in a folder OSDK, you simply have to add the following line in your AUTOEXEC.BAT:
Note that if you are using windows 2000 or later, you can also do this operation by creating a new environment variable called OSDK into the "advanced" menu of the system properties dialog box. You can go to the system properties using on of the following methods:
- Start > Settings > Control Panel > System
- Right-click My Computer; select Properties
- Press the keyboard shortcut WINDOWS+BREAK
Optionaly, you can also define a second environment variable that will be used to run Euphoric using DOSBox. Doing this will allow you to run it with sound and in a Windows friendly environment.
SET OSDKDOSBOX=C:\Program Files\DOSBox-0.65\dosbox.exe
After setting up the variable, you can test if everything works fine, by simply trying to build and execute one of the samples.
Just go to the folder "Osdk\sample\hello_world_simple", and launch "OSDK_BUILD.BAT". You should have the following display:
Building the program TEST1 at adress $800 Compiling MAIN.C - preprocess - compile - convert C to assembly code - cleanup output Build of TEST1.tap finished
If you have errors messages like "out of environment space", it means you will perhaps have to modify your "config.sys" file. At the end of the "config.sys" simply add the following line:
SHELL=C:\WINDOWS\COMMAND.COM /E:4096 /P
If you have this message instead:
== ERROR == The Oric SDK was not configured properly You should have a OSDK environment variable setted to the location of the SDK
it simply means you did something wrong in the section (2). Please not that some versions of windows require you to reboot the system before the modifications made to the environment became effective.
If it works, a BUILD folder should have appear, containing the following files:
- final.out => the raw binary file. Usefull for disk loading
- test1.tap => a tape file that is made from the raw file with a header appended
- xaerr.txt => the error messages outputed by the assembler
- xalbl.txt => the list of labels outputed by the assembler (usefull to check size/allignement)
Now, you just have to run OSDK_EXECUTE.BAT, that should launch the emulator and run your program. If you don't remember, it's F10 to quit.
Well done, you have compiled and run you first Oric program !
Alternatively you can use Wine: After some feedback and some attempts myself, I managed to successfully compile all the sample programs of the OSDK using Wine installed on a Ubuntu 6.06 LTS distribution. I think this is definitively better than nothing. The only part that do not work, is the Euphoric emulator itself, but this should be too much of a problem since the generated programs are compatible with all existing Oric emulators, including Oricutron.
Tested in Ubuntu Diaper Drake 6.06 LTS with Wine 0.9.23
Most probably you can install Wine directly by using the application installer/update of your Linux distribution. Alternatively you can go on the official Wine website, and download it from there:
Wine official website
Installing the OSDK in Wine:
You need to unzip the archive in the emulated windows drive. If we want to get it in C:/osdk, then you need to unzip in:
Setting the environment variable.
Just run regedit from Wine. You can do that by opening a terminal, and then type:
wine regeditat this point you need to create (if it does not yet exist) a new key
HKEY_CURRENT_USER/Environmentand there you create a new string:
- Name: OSDK
- Value: C:\OSDK
Just run the following command:
c: cd OSDKetc... you can try compiling a sample by going in
cd C:\osdk\sample\hello_world_simple osdk_build.bat
When this is done, you can test that everything works fine.Note: The creation of the Build folder is failing. Probably the existing test that fails.
No known problem - please signal any issue on the Cross development tools forum.
comments powered by Disqus