FlightGear Git on Windows: Difference between revisions

FlightGear Git on Windows (view source)

Revision as of 19:05, 26 August 2014

951 bytes removed , 26 August 2014

no edit summary

F-JJTH

577

edits

@@ Line 130: / Line 130: @@
 == 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.
-* 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.
+* Go to http://flightgear.simpits.org:8080/view/Win/job/Windows-nightly/ and download the <tt>flightgear-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</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.
-** 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''
-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.
 If your antivirus warns you of a trojan, ignore it. AVG and avast! are known for false positives.