FlightGear Git on Windows: Difference between revisions

Jump to navigation Jump to search
changed por mapserver, made more accurate update section, according to IRC
mNo edit summary
(changed por mapserver, made more accurate update section, according to IRC)
Line 19: Line 19:
Once msysGit is installed, browse to your <tt>FlightGear/data</tt> directory and right click. Choosing the "Git Bash" option pops up a command prompt. Add the following command and press Enter.
Once msysGit is installed, browse to your <tt>FlightGear/data</tt> directory and right click. Choosing the "Git Bash" option pops up a command prompt. Add the following command and press Enter.


  git clone git://gitorious.org/fg/fgdata.git D:/FlightGear/data
  git clone git://mapserver.flightgear.org/fgdata/


Now msysGit will pull the entire fgdata package into your <tt>FlightGear/data</tt> directory. '''This can take up to a couple of hours on slow internet connections!'''
Now msysGit will pull the entire fgdata package into your <tt>FlightGear/data</tt> directory. '''This can take up to a couple of hours on slow internet connections!'''
Line 25: Line 25:
===Getting the binary===
===Getting the binary===
Now we've got all the data, we need to have a binary, which contains the actual software that runs FlightGear. Go to ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 and download the latest <tt>fgrun+fgfs-osg-win32-git.zip</tt> file that is available. Unpack the file in your <tt>FlightGear/bin/win32</tt> directory.
Now we've got all the data, we need to have a binary, which contains the actual software that runs FlightGear. Go to ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 and download the latest <tt>fgrun+fgfs-osg-win32-git.zip</tt> file that is available. Unpack the file in your <tt>FlightGear/bin/win32</tt> directory.
If your antivirus warns you of a trojan, ignore. AVG and avast! are known for false positives.


===Running FlightGear===
===Running FlightGear===
Line 34: Line 36:
# Download the latest binary, as described in [[#Getting the binary|Getting the binary]] and overwrite the old one in <tt>FlightGear/bin/win32</tt> (instead you could rename the current binary's directory to something like win32_latest, in case the newer binary doesn't work well).
# Download the latest binary, as described in [[#Getting the binary|Getting the binary]] and overwrite the old one in <tt>FlightGear/bin/win32</tt> (instead you could rename the current binary's directory to something like win32_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!
# 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!
## Find out what date your just downloaded binary was created.
## Open Git Bash and go to your <tt>FlightGear/data/</tt> directory by using the "cd" command. Run "git pull" and let it update.
## Find out what's the version of the latest commit of the day before that day, through the [http://gitorious.org/fg/fgdata/commits/master Gitorious log]. A version-"number" looks like: da1ba93.
## Right click > Git Bash the following script to your <tt>FlightGear/data</tt> directory (replacing da1ba93 with your appropriate version).<br><pre>git checkout da1ba93 D:/FlightGear/data</pre>
173

edits

Navigation menu