224
edits
FlightGear Git on Windows: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 22: | Line 22: | ||
In fact, it is identical to the folder structure of your working copy of FG. | In fact, it is identical to the folder structure of your working copy of FG. | ||
== A first Git install (Develop) == | == A first Git install (Develop) == | ||
| Line 38: | Line 40: | ||
cd D:/FlightGear/data | cd D:/FlightGear/data | ||
In the event that the program refuses to | In the event that the program refuses to change directory, try this instead: | ||
cd "D:/FlightGear/data" | cd "D:/FlightGear/data" | ||
or, in some cases: | or, in some cases: | ||
cd | cd D: | ||
cd | cd Flightgear/data | ||
(replace the above paths with whatever you have created.) | (replace the above paths with whatever you have created.) | ||
| Line 104: | Line 106: | ||
git pull git://gitorious.org/fg/fgdata.git master | git pull git://gitorious.org/fg/fgdata.git master | ||
=== Getting the binary | |||
Now we've got all the data, we need to have a | |||
* Go to http://flightgear.simpits.org:8080/job/Win32-installer-Cmake/ and download the <tt>fgfs_win32_nightly_*.exe</tt> file. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin/win32</tt> directory. | |||
== A first Git install (User) == | |||
=== Obtaining data from Git === | |||
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: | |||
cd "D:/FlightGear/data" | |||
or, in some cases: | |||
cd D: | |||
cd Flightgear/data | |||
(replace the above paths with whatever you have created.) | |||
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 init | |||
Add the following command and press Enter. | |||
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. | |||
* Go to http://flightgear.simpits.org:8080/job/Win32-installer-Cmake/ and download the <tt>fgfs_win32_nightly_*.exe</tt> file. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin/win32</tt> directory. (Otherwise install it anywhere handy and copy the ''entire'' contents into the bin folder. | |||
* If you want to automate this, you can run the installer in silent mode by passing the /S parameter, the /D parameter can be used to set the target directory into which he needs to install the binaries: | * If you want to automate this, you can run the installer in silent mode by passing the /S parameter, the /D parameter can be used to set the target directory into which he needs to install the binaries: | ||
** e.g. ''fgfs_win32_vs2010_nightly_2.7.0.exe /S /D=C:\Flightgear\bin\win32'' | ** e.g. ''fgfs_win32_vs2010_nightly_2.7.0.exe /S /D=C:\Flightgear\bin\win32'' | ||
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 it. AVG and avast! are known for false positives. | ||
# Download the latest binary, as described in [[#Getting the binary|Getting the binary]] and overwrite the old one in <tt>FlightGear | == Running FlightGear (All) == | ||
# Update your <tt>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. | ||
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. | |||
== Keeping your FlightGear up to date (All) == | |||
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/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! | |||
## Open Git Bash and navigate to <tt>FlightGear\data</tt> directory. | ## Open Git Bash and navigate to <tt>FlightGear\data</tt> directory. | ||
## 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> | ## (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'' and let it update, this can take a while. | ## 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.. | ||
== Commiting changes == | == Commiting changes == | ||
Everything from here onwards is only for developers. | |||
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. | 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. | ||