FlightGear Git on Windows: Difference between revisions

Jump to navigation Jump to search
m
Robot: Cosmetic changes
mNo edit summary
m (Robot: Cosmetic changes)
Line 2: Line 2:
This document guides you through the installation process of the development version of [[FlightGear]] ([[Git]]) on Windows.
This document guides you through the installation process of the development version of [[FlightGear]] ([[Git]]) on Windows.


==A first Git install==
== A first Git install ==
===Pre-installation work===
=== Pre-installation work ===
Before we start, we will choose an installation directory. This can be any drive on your computer. In this document, we assume that you install FlightGear on the D:/ drive. Just replace the commands given in this document by your installation directory when using another drive or different directory root.
Before we start, we will choose an installation directory. This can be any drive on your computer. In this document, we assume that you install FlightGear on the D:/ drive. Just replace the commands given in this document by your installation directory when using another drive or different directory root.


Line 13: Line 13:
** <tt>data/</tt>
** <tt>data/</tt>


===Obtaining data from Git===  
=== Obtaining data from Git ===


You can use any Git software, however we advise to use msysGit (which will be used in this document). You can download it through [http://code.google.com/p/msysgit/downloads/list this link]. Follow the download/installation instructions that show up on your screen.
You can use any Git software, however we advise to use msysGit (which will be used in this document). You can download it through [http://code.google.com/p/msysgit/downloads/list this link]. Follow the download/installation instructions that show up on your screen.
Line 19: Line 19:
If you have a slow internet connection or you cannot keep your computer on for the long time that it takes for the data to download from the git server, follow Method 2.
If you have a slow internet connection or you cannot keep your computer on for the long time that it takes for the data to download from the git server, follow Method 2.


====Method 1:====
==== Method 1: ====


[[Image:msysgit_clone_fgdata.jpg|thumb|270px|The Git Bash window]]
[[File:msysgit_clone_fgdata.jpg|thumb|270px|The Git Bash window]]
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.


Line 37: Line 37:




====Method 2:====
==== Method 2: ====
Download this file : fgdata.bundle from http://peter-server.homelinux.net/fgdata/fgdata/
Download this file : fgdata.bundle from http://peter-server.homelinux.net/fgdata/fgdata/
or http://flightgear.mxchange.org/pub/fgfs/
or http://flightgear.mxchange.org/pub/fgfs/
Line 79: Line 79:
  git pull git://gitorious.org/fg/fgdata.git master
  git pull git://gitorious.org/fg/fgdata.git master


===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. The are two places where you can get such a binary (the later is updated more frequent):
Now we've got all the data, we need to have a binary, which contains the actual software that runs FlightGear. The are two places where you can get such a binary (the later is updated more frequent):
* 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.
* 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.
Line 86: Line 86:
If your antivirus warns you of a trojan, ignore. AVG and avast! are known for false positives.
If your antivirus warns you of a trojan, ignore. AVG and avast! are known for false positives.


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


==Keeping your FlightGear up to date==
== Keeping your FlightGear up to date ==
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 version.  
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 version.  


Line 98: Line 98:
## Run ''git pull'' and let it update, this can take a while.
## Run ''git pull'' and let it update, this can take a while.


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


Line 123: Line 123:
# ''git reset --hard HEAD''
# ''git reset --hard HEAD''
# ''git pull'' to make sure you can commit against the latest Git.
# ''git pull'' to make sure you can commit against the latest Git.
# ''git push <url> +master'' You will have to enter your SSH passphrase. Press Enter when you're done (note: your passphrase is hidden!). Git will now commit your work, this can take a long time, depending on the number of commits that have been made since you cloned fgdata.
# ''git push <url> +master'' You will have to enter your SSH passphrase. Press Enter when you're done (note: your passphrase is hidden!). Git will now commit your work, this can take a long time, depending on the number of commits that have been made since you cloned fgdata.
# Switch to your local branch, by ''git checkout rendering-checkboxes''
# Switch to your local branch, by ''git checkout rendering-checkboxes''
# Run ''git status -- .'' to show the status of the current directory.
# Run ''git status -- .'' to show the status of the current directory.

Navigation menu