4,400
edits
Building FlightGear - Windows: Difference between revisions
Jump to navigation
Jump to search
m
Robot: Cosmetic changes
(needs update to GIT) |
m (Robot: Cosmetic changes) |
||
| Line 11: | Line 11: | ||
Before you can compile FlightGear, you need to have the following installed on your computer: | Before you can compile FlightGear, you need to have the following installed on your computer: | ||
===C++ compiler=== | === C++ compiler === | ||
You may [http://www.microsoft.com/express/download/#webInstall download] the Express ("free" for personal use) version of Visual C++ 2008 from Microsoft. C++ Builder and Turbo C++ Explorer (by CodeGear, formerly by Borland) should work as well with some effort. We have not tried this. | You may [http://www.microsoft.com/express/download/#webInstall download] the Express ("free" for personal use) version of Visual C++ 2008 from Microsoft. C++ Builder and Turbo C++ Explorer (by CodeGear, formerly by Borland) should work as well with some effort. We have not tried this. | ||
| Line 22: | Line 22: | ||
Detailed installation instructions are available [http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=1995837&SiteID=1 here] (and [http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2888051&SiteID=1]). | Detailed installation instructions are available [http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=1995837&SiteID=1 here] (and [http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2888051&SiteID=1]). | ||
===Git=== | === Git === | ||
FlightGear uses [[FlightGear Git on Windows|Git]] for hosting the source code. You will need a Git client if you want to download the latest (development) source code for both FlightGear and SimGear. Traditionally, these are command line tools, but msysGit provides a graphic interface for Windows users. Download the installer for the latest stable version of [http://code.google.com/p/msysgit/downloads/list msysGit], run the installer, using all of its default settings (the installation destination folder is up to you). | FlightGear uses [[FlightGear Git on Windows|Git]] for hosting the source code. You will need a Git client if you want to download the latest (development) source code for both FlightGear and SimGear. Traditionally, these are command line tools, but msysGit provides a graphic interface for Windows users. Download the installer for the latest stable version of [http://code.google.com/p/msysgit/downloads/list msysGit], run the installer, using all of its default settings (the installation destination folder is up to you). | ||
===SVN=== | === SVN === | ||
OpenSceneGraph (OSG) uses Subversion (SVN) for version control. You will need an SVN client if you want to use the latest (development) source code for OpenSceneGraph. TortoiseSVN provides a graphic interface for Windows users. Download the installer for the latest stable version of [http://tortoisesvn.net/downloads TortoiseSVN], run the installer, using all of its default settings (the installation destination folder is up to you). | OpenSceneGraph (OSG) uses Subversion (SVN) for version control. You will need an SVN client if you want to use the latest (development) source code for OpenSceneGraph. TortoiseSVN provides a graphic interface for Windows users. Download the installer for the latest stable version of [http://tortoisesvn.net/downloads TortoiseSVN], run the installer, using all of its default settings (the installation destination folder is up to you). | ||
| Line 148: | Line 148: | ||
[[TerraSync]] is a convenient method to get actual scenery data without the need for download many megabytes of data before flying by synchronizing in [http://en.wikipedia.org/wiki/Apache_Subversion SVN manner]. TerraSync is part of the FlightGear sources and will be compiled by default with the other FlightGear binaries. To get TerraSync compiled properly you need to get the above mentioned "SVN developer library files". Extract the library and header files into your 3rdparty folder to the corresponding subfolders. | [[TerraSync]] is a convenient method to get actual scenery data without the need for download many megabytes of data before flying by synchronizing in [http://en.wikipedia.org/wiki/Apache_Subversion SVN manner]. TerraSync is part of the FlightGear sources and will be compiled by default with the other FlightGear binaries. To get TerraSync compiled properly you need to get the above mentioned "SVN developer library files". Extract the library and header files into your 3rdparty folder to the corresponding subfolders. | ||
== Getting OpenSceneGraph (OSG)== | == Getting OpenSceneGraph (OSG) == | ||
* '''Intro''' | * '''Intro''' | ||
| Line 156: | Line 156: | ||
Use [http://tortoisesvn.net/ Tortoise SVN] to fetch the lastest source of OSG. The URL for the project archive is http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.6. The destination folder should be '''OpenSceneGraph''' under your FlightGear project root directory. All other options can be left alone and are good to go as default. Wait until all files are downloaded from SVN. | Use [http://tortoisesvn.net/ Tortoise SVN] to fetch the lastest source of OSG. The URL for the project archive is http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.6. The destination folder should be '''OpenSceneGraph''' under your FlightGear project root directory. All other options can be left alone and are good to go as default. Wait until all files are downloaded from SVN. | ||
* '''Dependencies'''<br> | * '''Dependencies'''<br /> | ||
OSG depends on some external libraries from the GnuWin project<br> | OSG depends on some external libraries from the GnuWin project<br /> | ||
- [http://gnuwin32.sourceforge.net/packages/jpeg.htm Jpeg]<br> | - [http://gnuwin32.sourceforge.net/packages/jpeg.htm Jpeg]<br /> | ||
- [http://gnuwin32.sourceforge.net/packages/libpng.htm Png]<br> | - [http://gnuwin32.sourceforge.net/packages/libpng.htm Png]<br /> | ||
- [http://www.zlib.net/ ZLib]<br> | - [http://www.zlib.net/ ZLib]<br /> | ||
Download these packages and unzip them (including the folder structure) to your FG project folder\3rdparty. If you do not intend to create debug versions of OSG you can remove all links to debug files and *-bcc.lib in ...\3rdparty\lib. | Download these packages and unzip them (including the folder structure) to your FG project folder\3rdparty. If you do not intend to create debug versions of OSG you can remove all links to debug files and *-bcc.lib in ...\3rdparty\lib. | ||
A ready-to-use 3rd party archive, a detailed list of single dependencies and an explanation of the different dependencies can be found [http://www.openscenegraph.org/projects/osg/wiki/Downloads/Dependencies here]. | A ready-to-use 3rd party archive, a detailed list of single dependencies and an explanation of the different dependencies can be found [http://www.openscenegraph.org/projects/osg/wiki/Downloads/Dependencies here]. | ||
| Line 216: | Line 216: | ||
* '''Step 3''' - Build SimGear, either Release, Debug or both using VC++ 2008 (9.0) | * '''Step 3''' - Build SimGear, either Release, Debug or both using VC++ 2008 (9.0) | ||
<s>''Note:'' with the default settings, Visual C++ will yield many compiler warnings. Unfortunately, this is normal.</s><br> | <s>''Note:'' with the default settings, Visual C++ will yield many compiler warnings. Unfortunately, this is normal.</s><br /> | ||
''Note:'' Fortunately due to the efforts of developing the amount of warnings is getting less and less. Actually (June 2010) not more than 30 warnings should come up during compiling under Windows. | ''Note:'' Fortunately due to the efforts of developing the amount of warnings is getting less and less. Actually (June 2010) not more than 30 warnings should come up during compiling under Windows. | ||
| Line 240: | Line 240: | ||
TODO: Installation. | TODO: Installation. | ||
==Checking out the FlightGear data== | == Checking out the FlightGear data == | ||
The binary distribution package contains '''data''' for only a small subset of the existing aircraft and other objects. The instructions below tell you how to obtain the full set of data, in their latest, greatest form. | The binary distribution package contains '''data''' for only a small subset of the existing aircraft and other objects. The instructions below tell you how to obtain the full set of data, in their latest, greatest form. | ||