|
|
| (326 intermediate revisions by 23 users not shown) |
| Line 1: |
Line 1: |
| − | This HOWTO was written by ni1s to help Freespace fans get the latest bleeding-edge version of fs2_open from CVS. | + | {{Warning|This guide assumes some fundamental command line knowledge. As a rule of thumb, <b>do not copy & paste commands without fully understanding them</b>, especially as root. With great power comes great responsibility.}} |
| | + | <p></p> |
| | + | *[[Fs2_open_on_Linux/Introduction|Introduction]] |
| | + | *[[Fs2_open_on_Linux/Quickstart|Quickstart]] |
| | + | *[[Fs2_open_on_Linux/Preparation|Preparation]] |
| | + | **[[Fs2_open_on_Linux/Installing Git|Installing Git]] |
| | + | **[[Fs2_open_on_Linux/Installing the Development Libraries|Installing the Development Libraries]] |
| | + | *[[Fs2_open_on_Linux/Acquiring the Code|Acquiring the Code]] |
| | + | *[[Fs2_open_on_Linux/Pre-Compile Configuration|Pre-Compile Configuration]] |
| | + | **[[Fs2_open_on_Linux/Optimization|Optimization]] |
| | + | *[[Fs2_open_on_Linux/Compiling|Compiling]] |
| | + | **[[Fs2_open_on_Linux/Compile Script|Compile Script]] |
| | + | *[[Fs2_open_on_Linux/Acquiring the Game Data|Acquiring the Game Data]] |
| | + | **[[Fs2_open_on_Linux/Extracting data from CD|Extracting data from CD]] |
| | + | ***[[Fs2_open_on_Linux/Installing unshield|Installing unshield]] |
| | + | ****[[Fs2_open_on_Linux/Data Installation script|Data Installation script]] |
| | + | *[[Fs2_open_on_Linux/Post-Compile Configuration|Post-Compile Configuration]] |
| | + | **[[Fs2_open_on_Linux/Graphics Settings|Graphics Settings]] |
| | + | **[[Fs2_open_on_Linux/StartUp Script|StartUp Script]] |
| | + | *[[Fs2_open_on_Linux/Troubleshooting|Troubleshooting]] |
| | + | **[[Fs2_open_on_Linux/Common Compile-time Errors|Common Compile-time Errors]] |
| | + | ***[[Fs2_open_on_Linux/Novell SuSE and the Dependencies|Novell SuSE and the Dependencies]] |
| | + | ***[[Fs2_open_on_Linux/SDL: undefined reference to ...|SDL: undefined reference to ...]] |
| | + | ***[[Fs2_open_on_Linux/Missing -lGLU compile error|Missing -lGLU compile error]] |
| | + | **[[Fs2_open_on_Linux/Common Runtime Errors|Common Runtime Errors]] |
| | + | ***[[Fs2_open_on_Linux/ERROR: "Web cursor bitmap not found."|ERROR: "Web cursor bitmap not found."]] |
| | + | ***[[Fs2_open_on_Linux/I18n and Key mapping problems|I18n and Key mapping problems]] |
| | + | ***[[Fs2_open_on_Linux/Dedicated X Display|Dedicated X Display]] |
| | + | ***[[Fs2_open_on_Linux/Joystick Errors|Joystick Errors]] |
| | + | ***[[Mouse jumping to bottom right corner]] |
| | + | ***[[Fullscreen issue with multiple monitors]] |
| | | | |
| − | '''''WARNING! Compling from CVS will let you play with the most recent features and BUGS! Yes, BUGS, compile errors, strange game behavior and/or angry monkeys attacking you. Murphy's Law is very much in effect!'''''
| |
| | | | |
| − | == Installing CVS ==
| + | ---- |
| − | CVS stands for Concurrent Versions System and is a version control system used to record the changes in documents, such as source files. Developers use CVS so they can easily share their code changes among other developers. You will need this tool to download ("checkout" in CVS termology) fs2_open from the CVS server.
| |
| − | <br><br>
| |
| − | Use your package tool supplied by your distribution to download and install CVS.
| |
| | | | |
| − | '''Debian''' users want to:
| |
| − | apt-get install cvs
| |
| − | '''Gentoo''' users want to:
| |
| − | emerge cvs
| |
| | | | |
| − | '''NOTE: Radhat, Mandrake,Slackware and all the other distros should go here too,'''
| + | *[[Fs2_open_on_Linux/Compiling_PCS2|Compiling PCS2]] |
| − | '''but I have no knowlage on how these work, so if you do, please enlighten us.'''
| |
| | | | |
| − | == Installing Dev Libs ==
| + | [[Category:FreeSpace Open on Linux]] |
| − | You will also need OpenAL, libvorbis, OpenGL (most likely provided with your videocard driver), and LUA development packages (you dont need LUA if you dont need LUA scripting enabled, it wont go b0rk the compile if it cant find it). And ofcourse the GCC compiler and required make tools.
| |
| − | <br><br>
| |
| − | '''Debian''' users want to:
| |
| − | apt-get install libopenal-dev libvorbis-dev build-essential automake1.9 autoconf
| |
| − | '''NOTE:''' The ''build-essential'' meta package installs GCC4. This should work, but if you want GCC 3.4(gcc-3.4), add it to the apt-get line above.<br>
| |
| − | '''Gentoo''' users want to:
| |
| − | emerge openal libvorbis
| |
| − | '' NOTE: Gentoo Linux dose not distinguish between development and runtime libs. But you are''
| |
| − | '' a Gentoo user, so you already know that, don't you.''<br>
| |
| − | '''NOTE: Radhat, Mandrake,Slackware and all the other distros should go here too,'''
| |
| − | '''but I have no knowlage on how these work, so if you do, please enlighten us.'''
| |
| − | | |
| − | Before you begin, make sure you are situated in a a directory where you have write permissons. Your /home/user/ directory is pretty much a sure bet. I recommend that you create a permanent home/user/dev directory from which you run the CVS command, this way CVS will only update the files changed the next time you download the source.
| |
| − | | |
| − | == Using the source ==
| |
| − | | |
| − | === Downloading ===
| |
| − | | |
| − | Now get the source. Run from a terminal:
| |
| − | | |
| − | and then
| |
| − | | |
| − | The first cvs command tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login. The second command tells the CVS server on which we are now connected to that we want to checkout (co) the fs2_open module.
| |
| − | <br>
| |
| − | === CVS Checkout Script ===
| |
| − | Because 99,999% of all computer errors can be traced back to human-to-keyboard mishaps (linguistically proven by yours truly), I've written a quick bash script that will get the source for you. Save this and name it something appropriate like "get-fs2_open", and make it executable (<tt>chmod +x get-fs2_open</tt>).
| |
| − | #!/bin/bash
| |
| − | # CVS Checkout Script for fs2_open
| |
| − | CVS_ATTEMPT=0
| |
| − | until [ $CVS_ATTEMPT = 1 ]; do
| |
| − | | |
| − | cvs -z3 -d:pserver:anonymous:[email protected]:/home/fs2source/cvsroot co fs2_open && \ | |
| − | let CVS_ATTEMPT=1
| |
| − | done
| |
| − | ''NOTE: This script will run until it successfully downloaded fs2_open, abort it with CTRL+C (originally designed to hammer SourceForge's CVS server). Run the script from a terminal (<tt>./get-fs2_open</tt>) and wait for it to download the source files.''
| |
| − | | |
| − | === CVS Update Script ===
| |
| − | The code on CVS is in a constant state of change, and bugs that exist one day may be gone the next. Because of this, you'll want to occasionally update to a newer version and recompile. Rather than doing a full check out as you would with the previous script, you can update instead, which can save both bandwidth and time.
| |
| − | Save this and name it something appropriate like "update-fs2_open", and make it executable (<tt>chmod +x update-fs2_open</tt>).
| |
| − | #!/bin/bash
| |
| − | # CVS Checkout Script for fs2_open
| |
| − | CVS_ATTEMPT=0
| |
| − | until [ $CVS_ATTEMPT = 1 ]; do
| |
| − | | |
| − | cvs -z3 -d:pserver:anonymous:[email protected]:/home/fs2source/cvsroot update fs2_open && \ | |
| − | let CVS_ATTEMPT=1
| |
| − | done
| |
| − | | |
| − | === Building ===
| |
| − | | |
| − | In the directory you ran the CVS command from, a new directory will appear, namely fs2_open.
| |
| − | From that fs2_open directory run in a terminal:
| |
| − | ./autogen.sh
| |
| − | autogen.sh is a script that will generate the required makefiles. You will see alot of "checking for this" and "checking for that", this is actually the "configure" script (which can be run with <tt>./configure</tt> if you need to change the options) examining and configuring fs2_open for your system.<br>
| |
| − | It is possible to give autogen.sh configure options aswell, autogen.sh will pass them along to configure.
| |
| − | | |
| − | Now run:
| |
| − | make
| |
| − | Sit back and enjoy gcc work its magic.
| |
| − | | |
| − | === GL Compile Errors ===
| |
| − | | |
| − | On some Linux distributions (''Slackware'' for instance), compiling fails because a GL related library doesn't have a link in the <tt>/usr/lib</tt> directory. If the compile fails because it can't find <tt>-lGLU</tt>, here are two ways to fix it:
| |
| − | | |
| − | ==== As Root ====
| |
| − | | |
| − | If you have root access to the system, you can create a link to the library in question with just a little bit of command line magic. Go to a console and enter:
| |
| − | | |
| − | ln -s /usr/X11R6/lib/libGLU.so /usr/lib/libGLU.so
| |
| − | | |
| − | After that, you can run make again and it should finish compiling.
| |
| − | | |
| − | ==== As a Non-Root user ====
| |
| − | | |
| − | You don't have root access? Never fear, we can still fix the problem. It'll just be a tad more difficult.
| |
| − | | |
| − | Navigate to the <tt>fs2_open/code</tt> directory and locate a file named <tt>Makefile</tt> (not Makefile.rm or Makefile.in or Makefile.anything). Open it in your favorite text editor and make the following changes.
| |
| − | | |
| − | Find this line (line 457 in mine):
| |
| − | FS2_LDFLAGS = -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lGLU -lopenal -logg -lvorbis -lvorbisfile
| |
| − | | |
| − | And replace it with this:
| |
| − | FS2_LDFLAGS = -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lopenal -logg -lvorbis -lvorbisfile -L/usr/X11R6/lib -lGLU
| |
| − | | |
| − | | |
| − | Also find this one (line 565 in mine):
| |
| − | AM_LDFLAGS = -g -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lGLU -lopenal -logg -lvorbis -lvorbisfile
| |
| − | | |
| − | And replace it with this:
| |
| − | AM_LDFLAGS = -g -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lopenal -logg -lvorbis -lvorbisfile -L/usr/X11R6/lib -lGLU
| |
| − | | |
| − | Then rune <tt>make</tt> from the <tt>fs2_open</tt> directory, and watch the magic happen.
| |
| − | | |
| − | === Optimizing fs2_open ===
| |
| − | Optimizing fs2_open might have little or no effect, or improve performace greatly, I honestly have no clue.
| |
| − | You can specify your compiler flags with the configure script, se below.
| |
| − | ./configure CFLAGS="<your desired flags>"
| |
| − | If you got a Athlon-XP and want to play it safe, a good set of CFLAGS would be
| |
| − | ./configure CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer"
| |
| − | You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links.<br>
| |
| − | http://gcc.gnu.org/onlinedocs/gcc-3.4.1/gcc/Optimize-Options.html<br>
| |
| − | http://linuxreviews.org/howtos/compiling/safe-cflags/<br>
| |
| − | http://en.wikipedia.org/wiki/CFLAGS
| |
| − | === Using the Binaries ===
| |
| − | | |
| − | When the compile is done and if all went well, a binary executable will reside in the code directory ''fs2_open_r'' or ''fs2_open_d'' if you configured for a debug build. Copy the binary to directory where Freespace2 is installed, and you're all set to go.
| |
| − | | |
| − | === Changing Your Resolution ===
| |
| − | | |
| − | Odds are, you'll want to run fs2_open in a higher resolution than the default 640x480. Unfortunately, we Linux users don't have the swank launcher app that the Windows folks do. Instead, we'll be making a couple line changes to a config file. You will need to run fs2_open once before you can make the necessary changes, otherwise you won't have a configuration directory to work with.
| |
| − | | |
| − | The first thing we need to do is get into the fs2_open config directory, which is a hidden folder in your home directory. The fastest way to get there is to type the following in a console:
| |
| − | cd ~/.fs2_open
| |
| − | | |
| − | From here, open up fs2_open.ini in your text editor of choice (vi, EMACS, joe, pico, etc). You'll see something like the following:
| |
| − | [Default]
| |
| − | VideocardFs2open=OGL -(640x480)x16 bit
| |
| − | LastPlayer=MonkeyboyS
| |
| − | GammaD3D=1.0
| |
| − | | |
| − | Then change the Videocard line to the following:
| |
| − | VideocardFs2open=OGL -(1024x768)x32 bit
| |
| − | | |
| − | Save the file, and run fs2_open as you normally would. Voila! You're now in 1024x768 at 32bit color. Congratulations!
| |
| − | | |
| − | === Creating a Start Up Script ===
| |
| − | | |
| − | ''Note: This tutorial assumes some fundamental command line knowledge.''
| |
| − | | |
| − | In order to use all of the advanced engine features of fs2_open, you'll need to start the executable with a number of command line arguments. Instead of typing them in every time you want to start the game, why not create a script that does it for you?
| |
| − | | |
| − | Create a new file named start_freespace (or whatever you like) in your home directory. Open the file in your editor of choice, and paste the following:
| |
| − | #!/bin/sh
| |
| − | cd /path/to/your/freespace/
| |
| − | fs2_open_r -spec -glow -mipmap -jpgtga -orbradar -mod Media_VP
| |
| − | | |
| − | ''Note: You will need to edit this script before it will work properly. The second line must point to the directory where you installed fs2_open.''
| |
| − | | |
| − | The last line starts fs2_open with a number of arguments that turn on extra features. In the example, the game will use specular highlights, glow-mapping, mipmapping, jpg-tga conversion, the orb radar, and any MediaVPs installed to the /Media_VP directory. You should edit this line to use those features that your system supports.
| |
| − | | |
| − | More information about the available Command Line Arguments can be found at the [[Command-Line Reference]]
| |
| − | | |
| − | Once you've edited the file to your heart's content, make it executable:
| |
| − | chmod +x start_freespace
| |
| − | | |
| − | You can now type in start_freespace to start the game, or by clicking on start_freespace in your window manager. For convenience, you can copy it to your Desktop.
| |
