Yet Another Launcher.
FreeSpace 2 portable launcher.

1. =================== LINUX =================

To get the source:
	$ svn co svn://vega.livecd.pl/yal

To compile:
	$ cd yal/trunk
	$ ./build-all.sh

To run:
	Put the appriopriate launcher from bin dir to your game dir and run it.
	You can make a symlink to it in PATH dir and it will still work, just make
	sure the binary itself is in the game dir.

	Make sure you DON'T have GAMEDIR/data/cmdline_fso.cfg file. FS2_open
	merges flags from system wide and user wide files so if you do have
	one all flags from it will be forced and YAL won't reflect this.

Addons:
	If you want to have browser functionality you need to define BROWSERCMD
	in src/unix/System_unix.cpp. You can leave as it is now and make some
	'browser' script like I do and put it inside PATH dir:

	#!/bin/sh
	exec firefox "@"

Requirements:
	QT4 >= 4.3
	SDL >= 1.2.13
	OpenAL (openal-soft recommended!)

2. =================== WINDOWS =================

To run:
	Yal for windows is distributed in binary form.
	Put the appriopriate launcher to game dir and run from there.
	You should also get dll pack and put it either to game dir together
	with launcher, or to some PATH dir (like C:\Windows\System32).

To compile:
	If you want to compile it from source you need Qt SDK.
	Edit build-all.bat script where you should put a path to your
	SDK and run this script. If everything went well you should have
	binaries ready in bin dir.

3. =================== MAC OS X =================

	Help needed to implement platform specific functions.

4. =================== COMMOON =================

For now launcher uses the following files:
	1. ~/.fs2_open/launcher6.ini
	2. ~/.fs2_open/data/cmdline_fso.cfg
	3. GAMEDIR/MOD/mod.ini
	4. TEMPDIR/flags.lch

ad 1.
	This file is read on start if it exist. If it contains proper
	exe_filepath the latter is executed inside temporary dir and flags
 	are read from flags.lch (ad 4).
ad 2.
	If launcher6.ini does not exist or does not contain game_flags or
	they are empty there is an attempt to read cmdline_fso.cfg to fill
	initiall flags.
ad 3.
	This file is read from inside the active_mod dir or any other dir
	selected using GUI. Including game root dir used when actual mod name
	is empty.
