577
edits
FlightGear Git on Windows: Difference between revisions
Jump to navigation
Jump to search
bin/win32 and bin/win64 do no longer exist
(cat: Git; +section: Related content) |
(bin/win32 and bin/win64 do no longer exist) |
||
| Line 18: | Line 18: | ||
* <tt>FlightGear</tt> | * <tt>FlightGear</tt> | ||
** <tt>bin</tt> | ** <tt>bin</tt> | ||
** <tt>data</tt> | ** <tt>data</tt> | ||
| Line 131: | Line 130: | ||
== Getting the binary (All) == | == 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. | 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. | ||
* 32-bit: 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 | * 32-bit: 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</tt> directory. (Otherwise install it anywhere handy and copy the ''entire'' contents into the bin folder. | ||
* 64-bit: Go to http://flightgear.simpits.org:8080/job/Win64-installer-Cmake/ and download the <tt>fgfs_win64_nightly_*.exe</tt> file. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin | * 64-bit: Go to http://flightgear.simpits.org:8080/job/Win64-installer-Cmake/ and download the <tt>fgfs_win64_nightly_*.exe</tt> file. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin</tt> directory. (Otherwise install it anywhere handy and copy the ''entire'' contents into the bin folder. | ||
* If you want to automate this, the first time you download the binaries, make a note of the version number (to change it if needed in the examples below.) You can then run the installer in silent mode by passing the /S parameter. The /D parameter must be set to the folder into which the binaries must be installed. | * If you want to automate this, the first time you download the binaries, make a note of the version number (to change it if needed in the examples below.) You can then run the installer in silent mode by passing the /S parameter. The /D parameter must be set to the folder into which the binaries must be installed. | ||
** e.g. ''fgfs_win32_vs2010_nightly_2.11.0.exe /S /D=C:\Flightgear\bin | ** e.g. ''fgfs_win32_vs2010_nightly_2.11.0.exe /S /D=C:\Flightgear\bin'' | ||
** e.g. ''fgfs_win64_vs2010_nightly_2.11.0.exe /S /D=C:\Flightgear\bin | ** e.g. ''fgfs_win64_vs2010_nightly_2.11.0.exe /S /D=C:\Flightgear\bin'' | ||
Note that the version number changes each time a new version is released, so the ''2.11.0'' will have to be changed when this happens. | Note that the version number changes each time a new version is released, so the ''2.11.0'' will have to be changed when this happens. | ||
| Line 145: | Line 144: | ||
== Running FlightGear (All) == | == Running FlightGear (All) == | ||
Run <tt>FlightGear\bin | 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. | 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. | ||
| Line 154: | Line 151: | ||
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. | 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 | # 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! | # 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. | ||