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

Difference between revisions of "Building FlightGear"

From FlightGear wiki
Jump to: navigation, search
m
(New SVN is already adopted)
Line 2: Line 2:
  
 
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://www.gitorious.org/fg Gitorious.org]).
 
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://www.gitorious.org/fg Gitorious.org]).
 
SimGear 2.11+ now has experimental support for a libsvn replacement, people building from source are encouraged to help with testing and debugging this new feature:
 
 
{{cquote|<nowiki>First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40191.html|title=TerraSync libSVN replacement testing|author=James Turner|date=Tue, 11 Jun 2013 08:58:20 -0700}}</ref>|James Turner}}
 
 
{{cquote|<nowiki>So, as I've previously asked before, I really need people running from 'next'
 
to try with -DSG_SVN_CLIENT=1 when configuring SimGear, move their existing
 
TerraSync dir out the way, and test, test, test. I'm sure the new code isn't
 
100% trouble free (in particular I think there is still the occasional time
 
when it gets stuck not doing any more downloads until FG is restarted), but I
 
really don't want to move forwards with the code until I have a bit more
 
assurance it's not going to make everyone's setup crash 80% of the time, which
 
is what some people have reported.
 
 
Note this applies even if you 'don't use' terrasync since the SVN sync engine
 
is going to be used for other pieces of data as soon as it's stable. (I will be
 
adding a new preference to globally control whether FG works in online/offline
 
mode, of course)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40775.html|title=<nowiki>[Flightgear-devel] Built-in Svn client code crashing</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Fri, 20 Sep 2013 09:54:38 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}}
 
 
<references/>
 
  
 
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).
 
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).

Revision as of 11:07, 24 October 2013

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 Gitorious.org).

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 :