FlightGear build server: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
Line 12: Line 12:
* [http://flightgear.simpits.org:8080/job/Win32-installer/ Current Win32 nightly build]
* [http://flightgear.simpits.org:8080/job/Win32-installer/ Current Win32 nightly build]


(note there are no nightly builds for Linux - please [[Building_FlightGear_-_Linux|build from source]] ) Most easily with  [http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu/ download_and_compile.sh]
(note there are no nightly builds for Linux - please [[Building_FlightGear_-_Linux|build from source]] ) Most easily with  [http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu download_and_compile.sh]


In each case the installer contains all the code required (including OSG, OpenAL and so on) and the main FlightGear program, but '''no''' data directory. The Mac installer also lacks a launcher application, i.e can only be used from the Terminal. These builds are not intended for novice users - familiarity with FlightGear, especially the command-line arguments necessary to specify the data dir and scenery, is assumed.
In each case the installer contains all the code required (including OSG, OpenAL and so on) and the main FlightGear program, but '''no''' data directory. The Mac installer also lacks a launcher application, i.e can only be used from the Terminal. These builds are not intended for novice users - familiarity with FlightGear, especially the command-line arguments necessary to specify the data dir and scenery, is assumed.

Revision as of 07:29, 31 January 2011

Intro

The current source code (from Git) is automatically compiled every hour, by an installation of Hudson : http://flightgear.simpits.org:8080/

This compiles the current FlightGear and SimGear code on Linux, Mac and Windows, checking for compilation problems. Other platforms or compilers could be added if desired, for example FreeBSD, mingw or Intel C++. As part of the Mac and Windows build process, installers are produced and made available to download; these receive no testing or QA, but allow non-developers to run and test the latest code.

In the future, the build server will also be used to automate (and hence, streamline) the release process, so that pre-release, release and bug-fix builds can be produced with minimal manual work.

Nightly Builds

(note there are no nightly builds for Linux - please build from source ) Most easily with download_and_compile.sh

In each case the installer contains all the code required (including OSG, OpenAL and so on) and the main FlightGear program, but no data directory. The Mac installer also lacks a launcher application, i.e can only be used from the Terminal. These builds are not intended for novice users - familiarity with FlightGear, especially the command-line arguments necessary to specify the data dir and scenery, is assumed.

In general the data directory (fgdata) should be no older than the nightly build, or problems may arise, eg missing files or incompatible Nasal scripts.

When running a build, please do report problems via the developer mailing list or bug tracker (not the forums), but take care to mention that you're using a nightly build, and to specify when it was built.

Related Discussions