Building FlightGear: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
mNo edit summary
(removing obsolete quote)
Tags: Mobile edit Mobile web edit
(20 intermediate revisions by 11 users not shown)
Line 1: Line 1:
The FlightGear developers generally release a stable packaged version of FlightGear, with an easy install wizard, about once or twice a year.  For convenience, most FlightGear users download and install these packages.


However, the source files used to build the whole FlightGear package are continuously being developed by dozens of contributors, who collaborate using CVS to create a new "unstable" version every few days. If you want to use one of these unstable versions, or tinker with the source files to create your own custom version, the pages below describe how to compile the FlightGear package from the CVS source files.
The [[FlightGear]] developers generally release a stable packaged version of FlightGear, with an easy install wizard, about once or twice a year. For convenience, most FlightGear users download and install these packages.
 
However, the source files used to '''build the whole FlightGear package''' are continuously being developed by dozens of contributors, who collaborate using the source code management system [[Git]] to create a new "unstable" version every few days. If you want to use one of these unstable versions, or tinker with the source files to create your own custom version, the pages below describe how to compile the FlightGear package from the Git source files (repository at [http://sourceforge.net/projects/flightgear http://sourceforge.net]).
 
If you'd like to use an integrated development environment, illustrated instructions for building FlightGear and its dependencies can be found in [[Howto:Build FlightGear with NetBeans using CMake]], this should work on both, Windows and Linux systems (NetBeans being a cross-platform IDE).
 
Another option to run the latest code without having to compile everything yourself, is using a precompiled binary provided by the [[FlightGear Build Server]] which is based on Jenkins.


'''Building FlightGear''' may refer to:
'''Building FlightGear''' may refer to:
* [[Superbuild|Using CMake Superbuilds]]
* [[Superbuild on Windows|Using CMake Superbuild - Windows]]
* [[Building using CMake]]
* [[Building using CMake - Windows]]
* [[Building FlightGear - Linux]]
* [[Building FlightGear - Linux]]
* [[Scripted Compilation on Linux Debian/Ubuntu|Building using Linux bash script]]
'''Old pages''' :
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ Building FlightGear - Mac OS X]
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ Building FlightGear - Mac OS X]
* [[Building FlightGear - Windows]]
* [[Updating FlightGear on Windows]] - get a recently updated version without compiling
* [[Updating FlightGear on Windows]] - get a recently updated version without compiling
{{Building}}

Revision as of 19:48, 21 February 2019

The FlightGear developers generally release a stable packaged version of FlightGear, with an easy install wizard, about once or twice a year. For convenience, most FlightGear users download and install these packages.

However, the source files used to build the whole FlightGear package are continuously being developed by dozens of contributors, who collaborate using the source code management system Git to create a new "unstable" version every few days. If you want to use one of these unstable versions, or tinker with the source files to create your own custom version, the pages below describe how to compile the FlightGear package from the Git source files (repository at http://sourceforge.net).

If you'd like to use an integrated development environment, illustrated instructions for building FlightGear and its dependencies can be found in Howto:Build FlightGear with NetBeans using CMake, this should work on both, Windows and Linux systems (NetBeans being a cross-platform IDE).

Another option to run the latest code without having to compile everything yourself, is using a precompiled binary provided by the FlightGear Build Server which is based on Jenkins.

Building FlightGear may refer to:

Old pages :