27
edits
m (→Getting the binary: (made a little mistake in the layout!)) |
|||
Line 88: | Line 88: | ||
=== 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. | Now we've got all the data, we need to have a binary, which contains 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 | * 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. | ||
* 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'' | ** e.g. ''fgfs_win32_vs2010_nightly_2.7.0.exe /S /D=C:\Flightgear\bin'' | ||
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. |
edits