Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G


Jump to: navigation, search

Scripted Compilation on Linux Debian/Ubuntu

32 bytes added, 19:11, 8 March 2011
Robot: Cosmetic changes
Necessary packages are installed via the apt-get system while libraries not included in the repositories are downloaded and compiled on the fly (i.e. [[Plib]], [[Simgear]] and [[OSG]]).
===List of compiled programs===
The script is able to download and compile:
* Flightgear (And all the data needed to use it)
* [[Fgrun]]
* [[FGCOM]]
* [[Terrasync]]
You can download the script here: [http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh download_and_compile.sh]
There is also another option for building FG and all its dependencies in an automated fashion, please refer to: http://geoffmclane.com/fg/fgfs-052.htm
To run download_and_compile.sh, just save it in a directory called for example: ~/fg_tools
then execute it (no need to execute it as root).
Once all will be finished, you will sucessfully get all the programs installed in the ~/fgfs directory.
===Launching FlightGear===
To run your new git installation of Flightgear you have to launch the ''run_fgfs.sh'' command under the same folder, for example:
===Launching Fgrun===
For many users it's more comfortable having Flightgear launched by the graphical utiliy Fgrun which is installed as well in the same folder. You have to launch the ''run_fgrun.sh'' command, for example:
===Launching FGCOM===
FGCOM is the system used by flightgear to simulate radio communications between users. Launch it using the ''run_fgcom.sh'' command:
===Launching FGComGui===
FgComGui is a GUI wrapper to launch fgcom.
===Launching Atlas===
Atlas provides a map for Flightgear, use it launching: ''run_atlas.sh''
===Launching Terrasync===
Your Flightgear compilation comes with the Terrasync program too, so if you want to use it:
Where: ''/folder/with/sceneries'' is the folder containing the sceneries data.
Then launch fgfs with the '''--fg-scenery=/folder/with/sceneries --atlas=socket,out,5,localhost,5500,udp''' option
===Compilation errors===
Here we are, no fear, if you wish to use programs from the cvs/svn/git repositories, you might face compilation errors that will prevent you to have a working copy of one or more of the programs provided by this script. What can be the causes that prevent us from a successful compiling? As far as I know those:
# Software developers introduce a new functionality with a new piece of code that prevents the compilation under your architecture, this can happen working with cvs/svn/git sources.
Sometimes it happens that the script fails to compile only fgrun,fgcom or atlas, if you then see the run_fgfs.sh file it means that Flightgear installation was successful and you can safely run it.
The script by default (without any option) will only compile Flightgear and Fgrun. To make it compile all, you need to launch the script with the ''ALL'' parameter. i.e.:
===Compiling only one program===
If you wish to recompile only one of the programs you can launch the script with one of the following parameters:
* PLIB (to compile and install only plib)
* ATLAS (to compile and install only Atlas)
===Fast updating===
There is a second parameter ''UPDATE'' that allows you to just update your installation. i.e.:
This will only update FGFS
===Compiling last stable versions (Experimental)===
Event if the script fetches data and sources from bleeding edge developers repositories (which sometimes do not compile), you can still force the script to download latest know versions of the software that was compiling successfully adding the -s option.
How it works ? Inside the script there is a small list with lates known versions of successfully compiling revisions, it will download from svn/git that specific revisions, which have been found able to compile together.
===Advanced options===
* Skip download of packages using '''-p n''' option
* Skip compilation of programs using '''-c n''' option
this will only recompile modifications and reinstall them.
===Multicore Acceleration===
Using the option '''-j x''' (where x is the number of your CPU-Cores you wish to assign to the job) will speed up the whole compilation process considerably.
==Disk usage==
Having both compiled program, source codes and data from git requires some hard disk space: It will take you something like 7 GB of space.
If you don't have a fast machine, it will require you also some hours of compilation time.
[[nl:Compileren_met_een_Script_op_Linux_DebianCompileren met een Script op Linux Debian/Ubuntu]]

Navigation menu