Keeping FlightGear (win32) up to date without compiling: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(First part of the tutorial)
 
m (Redirected page to FlightGear Git on Windows)
 
(36 intermediate revisions by 8 users not shown)
Line 1: Line 1:
===Keeping FlightGear (Windows) up-to-date without
#REDIRECT [[FlightGear Git on Windows]]
compiling the sourcecode===
 
There are three easy steps to keep up with the actual development of FlightGear:
 
==First step:==
You can find the latest FlightGear development branch already compiled as a Windows(TM)
executable file (fgfs.exe) at [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32  ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32]by Frederic Bouvier. There a lot of precompiled binaries, the newest one together with the latest FGRun. There are irregular updates, sometimes even nearly weekly. So check the filename for the latest
version.
fgfs-win32-20060710.zip tells you that it is the version of July 10, 2006. The download size will be
about then 5 MB.
 
==Second step:==
It is obligatory to combine a new FlightGear binary mainprogram with the matching FlightGear data
not only to get the newest developments but as configuration files or dataformats might have got
changed.
You have to download the newest data from
[http://cvs.flightgear.org/cgi-bin/viewvc/viewvc.cgi/data/ http://cvs.flightgear.org/cgi-bin/viewvc/viewvc.cgi/data/]
 
At the bottom of the page you will find the link "Download tarball".
This is a pretty big amount of bytes (about 1 Gb!) so you should have a fast internet
connection.
You have to unzip the download before copying it into [YourFlightGearFolder].

Latest revision as of 22:32, 16 June 2010

Redirect to:

Retrieved from "https://wiki.flightgear.org/w/index.php?title=Keeping_FlightGear_(win32)_up_to_date_without_compiling&oldid=22327"