Difference between revisions of "Running Oolite-Windows"
(→Building Oolite from source) |
(→Building Oolite from source) |
||
Line 50: | Line 50: | ||
##<code>make clean </code> | ##<code>make clean </code> | ||
##<code>make </code> | ##<code>make </code> | ||
− | # Towards the end you'll get the following error: | + | At this point Ean - from the Oolite board - reports that |
+ | {| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .1em; cellpadding: 0; cellspacing: 0; color: #000000;" | ||
+ | |I had to add /Local/include to the include search path - dunno why but it works now. | ||
+ | |} | ||
+ | |||
+ | |||
+ | 11. Towards the end you'll get the following error: | ||
<pre> | <pre> | ||
cp: cannot stat `shared_debug_obj/oolite.exe': No such file or directory | cp: cannot stat `shared_debug_obj/oolite.exe': No such file or directory | ||
Line 56: | Line 62: | ||
</pre> | </pre> | ||
Don't panic! Now we need to move a few files around... | Don't panic! Now we need to move a few files around... | ||
− | |||
− | 12. From windows, copy oolite.exe from <code>C:\GNUstep\Local\oolite\trunk\obj</code> to <code>C:\GNUstep\Local\oolite\trunk\oolite.app </code> | + | Ean has provided a nice fixwin script to move those files automatically. Grab it from inside this zip file [http://wiki.alioth.net/images/3/3f/Fixwin.zip], and put it in C:\GNUstep\Local\oolite\trunk\ |
+ | |||
+ | If everything went well, these are the last two lines you need to type to get oolite to run: | ||
+ | |||
+ | # <code>fixwin</code> | ||
+ | # <code>openapp oolite.app </code> | ||
+ | |||
+ | |||
+ | If you have a problem running fixwin, do the following instead: | ||
+ | |||
+ | |||
+ | 12. Still inside the GNUstep shell, type <code>mv oolite.debug oolite.app </code> | ||
+ | |||
+ | 13. From windows, copy oolite.exe from <code>C:\GNUstep\Local\oolite\trunk\obj</code> to <code>C:\GNUstep\Local\oolite\trunk\oolite.app </code> | ||
+ | |||
+ | 14. Now copy all the dlls your installed copy of oolite 1.70-test. Assuming that you installed it to the default directory, copy all dlls from <code>C:\Program Files\Oolite\oolite.app\</code> into <code>C:\GNUstep\Local\oolite\trunk\oolite.app </code> | ||
− | + | 15. Now you also need to copy all the dlls from <code>C:\GNUstep\Local\bin</code> to <code>C:\GNUstep\Local\oolite\trunk\oolite.app</code>. Overwrite all the duplicates. | |
− | |||
− | |||
− | |||
− | |||
+ | 16. We're almost ready to launch the compiled oolite! From inside the GNUstep shell: | ||
+ | # <code>cd /Local/oolite/trunk </code> | ||
+ | # <code>openapp oolite.app </code> | ||
Revision as of 23:47, 9 March 2008
Contents
Overview
The Windows port of Oolite is built from the same source as the Linux and OS-X versions, and has all the features of those versions.
All OXPs should be compatible with the Windows port.
Getting and installing the game
The game may be downloaded from the BerliOS project page for Oolite-PC. The installer is also mirrored at ftp://ftp.alioth.net/oolite . The current, stable version is 1.65.
To install, run the executable that you have just downloaded. You will get the familiar Windows installer.
A regular build of changes from the SVN source is being carried out on a regular basis. The complete installer above must be installed before any of the updates will work. The update filename changes with each build, so get the latest update file by following the link here: [1].
The game has been tested on Windows XP and Windows 2000. It will not run on the DOS-extender versions of Windows such as Windows 95, 98 or ME. It is expected it will run with Vista, so long as drivers are available for the hardware you have. You are advised to run the latest 3D graphics drivers from your 3D card manufacturer.
Running the game
Find the Oolite icon in the Start -> Programs menu and click on it. Alternatively double click the Oolite program icon on the desktop. Note that the following key combination will get you out of 'graphics related trouble':
Shift-Escape: Quit Oolite immediately
If your game seems to have unreasonably low fps performance (check this in-game by hitting SHIFT-F) it is strongly recommended you visit your graphic cards' suppliers website and download and install the latest drivers.
Installing OXPs
You will need to find where the oolite.app folder is placed: it should be in C:\Program Files\Oolite. Create an AddOns folder beside the oolite.app folder. Put OXPs in here. Note that some OXPs when unzipped contain a folder with a README file and then the OXP - in this case, it's best to unzip the OXP somewhere other than AddOns and copy the OXP folder once unpacked into AddOns.
Notes for amd64 users
No builds for 64-bit versions of Windows have yet been made, however, given the proper availability of graphics and sound drivers, the 32-bit version should run on 64-bit Windows. 32 bit Windows running on amd64 hardware should not have an issue.
Building Oolite from source
Update: 24-Jan-2008 These are the latest instructions for building Oolite on Windows. Acknowledgments and thanks to Kaks for providing them:
Important note: It is recommended that all packages for Windows be installed in paths that do not contain spaces. The same recommendation applies for the Windows username of the account the build is performed from. There have been reports of MSYS/make problems in such cases.
- If you have an older version of GNUstep(GNUstep-base-1.11.1-gui-0.10.1-3 - from the wiki howto), uninstall it, then delete its root directory if it's still there(c:\GNUstep).
- Google & download the following 2 packages, and - this is important - install them in this sequence: gnustep-system-0.9.1-setup.exe, gnustep-core-0.9.2-setup.exe
- Google & download tortoiseSVN, install.
- You need to have installed the latest oolite test download (1.70-test atm). Also required is the dependencies file for Windows. Download Local_20080124.zip [2].
- Go to the Windows Start menu, navigate to and select Start>Programs>GNUstep>Shell
- At the prompt :
mkdir /Local
mkdir /Local/oolite
mkdir /Local/oolite/trunk
. The first slash & the upper case L are very important!
- From windows, extract the directories inside Local_20080124.zip to
C:\GNUstep\Local
- Still from windows go to
C:\GNUstep\Local\oolite\trunk
- It's empty. Right click>SVN checkout. The repository is
svn://svn.berlios.de/oolite-linux/trunk
. Wait for it to finish. - From inside the GNUstep shell
export PATH=$PATH:/Local/bin
cd /Local/oolite/trunk
make clean
make
At this point Ean - from the Oolite board - reports that
I had to add /Local/include to the include search path - dunno why but it works now. |
11. Towards the end you'll get the following error:
cp: cannot stat `shared_debug_obj/oolite.exe': No such file or directory make: *** [after-all] Error 1
Don't panic! Now we need to move a few files around...
Ean has provided a nice fixwin script to move those files automatically. Grab it from inside this zip file [3], and put it in C:\GNUstep\Local\oolite\trunk\
If everything went well, these are the last two lines you need to type to get oolite to run:
fixwin
openapp oolite.app
If you have a problem running fixwin, do the following instead:
12. Still inside the GNUstep shell, type mv oolite.debug oolite.app
13. From windows, copy oolite.exe from C:\GNUstep\Local\oolite\trunk\obj
to C:\GNUstep\Local\oolite\trunk\oolite.app
14. Now copy all the dlls your installed copy of oolite 1.70-test. Assuming that you installed it to the default directory, copy all dlls from C:\Program Files\Oolite\oolite.app\
into C:\GNUstep\Local\oolite\trunk\oolite.app
15. Now you also need to copy all the dlls from C:\GNUstep\Local\bin
to C:\GNUstep\Local\oolite\trunk\oolite.app
. Overwrite all the duplicates.
16. We're almost ready to launch the compiled oolite! From inside the GNUstep shell:
cd /Local/oolite/trunk
openapp oolite.app
The instructions below are valid only for versions prior to 1.70, only use them as an alternative if the updated ones fail for whatever reason.
- Download and install the necessary software
- Get the source and build it (note, the source comes from the oolite-linux project)
- Start the GNUstep command line (Start -> Programs -> GNUstep Development -> MSYS for GNUstep) and issue the following commands:
cd $GNUSTEP_LOCAL_ROOT
export PATH=$PATH:$GNUSTEP_LOCAL_ROOT/bin
mkdir oolite
cd oolite
svn checkout svn://svn.berlios.de/oolite-linux/trunk
cd trunk
make
- To run the game in the build environment:
- Before running the first time:
cp $GNUSTEP_LOCAL_ROOT/bin/*.dll oolite.app
openapp oolite.app
- Before running the first time:
Assuming you have installed one of Nic's releases as detailed above, you can easily keep updating the installation from the latest source. In the $GNUSTEP_LOCAL_ROOT/oolite/trunk
directory, issue the commands:
export PATH=$PATH:$GNUSTEP_LOCAL_ROOT/bin
svn up
rm -rf oolite.app/Resources; make
You only need to issue the export PATH command when you first start the command line. The rm -rf command before make is required because GNUstep for Windows cannot parse the XML plist file format, and the build fails when it tries to read one of these generated each time the build is performed. This failure is not important, and the process still works, but it is annoying.
Then use the following script to copy the new files over the existing installation:
OA="/c/Program Files/Oolite/oolite.app" cd $GNUSTEP_LOCAL_ROOT/oolite/trunk if [ oolite.app/oolite.exe -nt "$OA/oolite.exe" ]; then echo "Updating oolite.exe" cp oolite.app/oolite.exe "$OA/oolite.exe" fi for a in AIs Config Images Models Music Sounds Textures; do for b in Resources/$a/*; do c=`basename $b` if [ $b -nt "$OA/Contents/Resources/$a/$c" ]; then echo "Updating with $b" cp $b "$OA/Contents/Resources/$a/$c" fi done done
If you want to edit the source, Notepad++ has good Objective-C support and is free: [7]
Also see the Oolite-PC forum: [8]