Aleph One install guide
From Traxus
Contents |
Mac OS X
Before continuing, make sure you have downloaded Aleph One and at least one Scenario.
Single scenario
- Unpack the scenario data
- Unpack the Aleph One application
- Put the Aleph One application into the scenario's folder
After performing these steps, you should be able to just double-click on the Aleph One application and see the scenario's title screen. If it doesn't work, consult the Troubleshooting section.
Multiple scenarios
Each scenario needs its own copy of the Aleph One application.
Installing extra maps or enhancements
Troubleshooting
Windows
Before continuing, make sure you have downloaded Aleph One and at least one Scenario.
Single scenario
- Unpack the scenario data
- Unpack the Aleph One application
- Put the Aleph One application into the scenario directory.
After performing these steps, you should be able to just double-click on the Aleph One application and see the scenario's title screen. If it doesn't work, consult the Troubleshooting section.
Multiple scenarios
Each scenario needs its own copy of the Aleph One application.
Installing extra maps or enhancements
Troubleshooting
Linux
Before continuing, make sure you have downloaded Aleph One and at least one Scenario.
Compiling and installing Aleph One
If you happen to use Gentoo, you're in luck; you can simply run emerge alephone to compile and install Aleph One and all of its dependencies. You will also eventually be able to install some scenarios that way too. Until then, you should skip to the section for installing the scenario data.
Prerequisites
- libGL
- libsdl
- libboost
- liblua (optional)
- libspeex (optional)
Note that you will also need the development tools for your distribution, as well as the development versions of the packages listed above.
Unpacking the source code
tar -xzvf AlephOne-20060506.tar.gz cd AlephOne-20060506
Configuration
./configure
(this guide will refer to the install location (/usr/local in this case) as $PREFIX later on)
or
./configure --prefix=$PREFIX
(this guide will refer to $PREFIX later on)
Compilation
make
Installation
sudo make install
or
su -c "make install"
Single scenario
The easiest way to install a single scenario is to put it in the AlephOne data directory, which is $PREFIX/share/AlephOne. Note that you will probably have to become root (using sudo or su) before you can install it there.
You should be able to launch the scenario by typing alephone in a terminal. If it doesn't work, consult the Troubleshooting section.
Note to Gentoo users: Gentoo installs Aleph One with a $PREFIX of /usr, but the AlephOne data directory is located at /usr/share/games/AlephOne.
Multiple scenarios
This is where it gets a bit complicated. You will probably want to set up a directory for each scenario in $PREFIX/share. For example, if you want to install Marathon Infinity and Rubicon, you might want to put them in $PREFIX/share/marathon-infinity and $PREFIX/share/marathon-rubicon, respectively. You will need to create these directories yourself. Again, you will probably need to become root using sudo or su to do this.
Once you have the data in the appropriate directories, you will want to create a wrapper script for each scenario. Here is one for Marathon Infinity, using the directory mentioned earlier:
#!/bin/sh export ALEPHONE_DATA=$PREFIX/share/marathon-infinity:$PREFIX/share/AlephOne $PREFIX/bin/alephone "$@"
Again, replace $PREFIX with the install location you provided in the configuation step.
Save the wrapper script in $PREFIX/bin with an appropriate name (such as marathon-infinity), and make it executable, like so:
chmod a+x $PREFIX/bin/marathon-infinity
You should then be able to launch the scenario by typing the name of its wrapper script. If it doesn't work, consult the Troubleshooting section.
Note to Gentoo users: Installation of multiple scenarios is much easier than those steps above. Just create a directory in /usr/share/games with a name beginning in alephone- (for example, /usr/share/games/alephone-infinity), and put the scenario data there. Then make a symbolic link to the provided wrapper script with the appropriate name, like so:
ln -s alephone.sh /usr/games/bin/alephone-infinity
The wrapper script will automatically find the directory whose name matches the link.
