FlightGear Git on Windows: Difference between revisions

{{Note|Some files demand that CR/LF (carriage return/line feed) line breaks are preserved.  To avoid errors or problems later, run these commands:

Download the <tt>fgdata.bundle</tt> from or http://flightgear.mxchange.org/pub/fgfs/. Use <tt>Right mouseclick > Save target as</tt> on the file, if you end up with a webpage full of weird characters.

You might want to use the <tt>fgdata.bundle.torrent</tt>, as this will give you pause and resume.

After downloading, download the MD5 checksum, fgdata.bundle.md5, from the same site.

Verify the checksum of your file using any free Md5 checking utility available on the internet like this one :  http://www.bullzip.com/products/md5/info.php

The generated checksum should match the downloaded one. If not, redownload.

Copy this file to your <tt>FlightGear\data</tt> directory.

Open Git Bash via <tt>C:\Program Files\msysgit\Git Bash</tt> (the shortcut) and run (replacing the path with your preferred path):

Now msysGit will expand the entire fgdata.bundle package into <tt>FlightGear\data\fgdata</tt>.

Wait for a few minutes until it is completed (the flashing cursor will reappear after it is done).

If your get this error:

run this command:

It should be fixed now. Go back to Flightgear/data.

Now pull from GIT to update to the latest files using  

git pull git://gitorious.org/fg/fgdata.git master

== A first Git install (User) ==

 

Open Git Bash via <tt>C:\Program Files\msysgit\Git Bash</tt> (or open via the shortcut) and run (replacing the path with your preferred path):

cd D:/FlightGear/data

In the event that the program refuses to change directory, try this instead:

or, in some cases:

 

 

Then run the following, to initialise a Git repository. This should create a .git folder in data/. (It will probably be a hidden folder.)

git pull --depth 1 git://gitorious.org/fg/fgdata master

This can be 3GB or more. Unfortunately, there is no way of doing pause and resume.

When it is finished, you will have the entire data structure of FG, including ''all'' the aircraft.

== Getting the binary (All) ==

Now we've got all the data, we need to have a binaries, (.exe and .dll files) which contain the actual software that runs FlightGear.

* The installer is intelligent: it detects whether you have a 32-bit or 64-bit system.

If your antivirus warns you of a trojan, ignore it. AVG and avast! are known for false positives.

Run <tt>FlightGear\bin\fgrun.exe</tt> to launch the [[FlightGear Wizard]], or run <tt>FlightGear\bin\fgfs.exe</tt> by commandline.  

If using fgrun.exe You will have to use Prev to go back to the first page and change the entries for Executable and FG_ROOT to your new folders. Most of the time you can leave FG_SCENERY as it is. Until there is a major development in FG's scenery handling methods.

Of course you want to keep FlightGear up to date, to keep current with the latest developments. Else you don't have a reason to use the development (or cutting-edge) version.  

# Download the latest binary, as described in [[#Getting the binary|Getting the binary]] and overwrite the old one in <tt>FlightGear\bin</tt> (instead you could rename the current binary's directory to something like bin_latest, in case the newer binary doesn't work well).

# Update your <tt>FlightGear\data</tt> directory, to match it with the binary. For smooth operations, it is very important to have data and a binary from matching dates!

## Open Git Bash and navigate to <tt>FlightGear\data</tt> directory.

## (Developers) Run ''git reset --hard'' to revert any local changes. <font color="red">'''Note: this will delete all local changes! If you made local changes, make sure to backup those first, outside your FlightGear data directory! Or, better, learn to commit your changes to your local git repository.'''</font>

## Run ''git pull git://gitorious.org/fg/fgdata'' and let it update, this can take a while, depending on how long ago you last did an update..

As a developer, you probably want to share your work with the world. For FlightGear, most developers do this by committing stuff to the Git repository.

* [[FlightGear Git: core developers]].