648
edits
Line 138: | Line 138: | ||
Now that we've got all the data, we need to have a binaries (<code>.exe</code> and <code>.dll</code> files) which contain the actual software that runs FlightGear. | Now that we've got all the data, we need to have a binaries (<code>.exe</code> and <code>.dll</code> files) which contain the actual software that runs FlightGear. | ||
Go to http://download.flightgear.org/builds/nightly/ and download the one of the binaries. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin</tt> directory. The installer will detect whether you have a 32-bit or 64-bit system. | Go to http://download.flightgear.org/builds/nightly/ and download the one of the binaries (as you have downloaded the data using git, you do not need the <code>-full.exe</code>. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin</tt> directory (make sure the installer points to the directory above the bin directory created in pre-installation work - otherwise you get a bin directory below the bin directory). The installer will detect whether you have a 32-bit or 64-bit system. | ||
{{Note|If your antivirus warns you of a Trojan horse, ignore it. AVG and avast! are known for false positives.}} | {{Note|If your antivirus warns you of a Trojan horse, ignore it. AVG and avast! are known for false positives.}} |
edits