Superbuild: Difference between revisions

Jump to navigation Jump to search
Line 27: Line 27:
* VisualStudio 2010 (for the moment, other variations such as 2012 need some work)
* VisualStudio 2010 (for the moment, other variations such as 2012 need some work)
* CMake for Windows  
* CMake for Windows  
 
* SVN (see [[Tools of the Trade#Source Code Management / Revision Control Systems|here]].)
We assume you have cloned fgmeta in C:\FGFS\fgmeta. All the example paths below work just fine if you replace C:\FGFS with G:\MyAwesomeDir\AnySubDir.
We assume you have cloned fgmeta in C:\FGFS\fgmeta. All the example paths below work just fine if you replace C:\FGFS with G:\MyAwesomeDir\AnySubDir.
(Spaces in the paths are untested and might cause issues, but might work fine)
(Spaces in the paths are untested and might cause issues, but might work fine)
Line 35: Line 35:
* Run the CMake GUI, and select C:\FGFS\fgmeta as the source dir, and C:\FGFS\metabuild as the build dir
* Run the CMake GUI, and select C:\FGFS\fgmeta as the source dir, and C:\FGFS\metabuild as the build dir
* Run 'Configure' once, and set CMAKE_INSTALL_PREFIX to C:\FGFS\metabuild\install (this step will be automated soon)
* Run 'Configure' once, and set CMAKE_INSTALL_PREFIX to C:\FGFS\metabuild\install (this step will be automated soon)
: If Subversion_SVN_EXECUTABLE is marked red, look for svn.exe in the folders under where SVN is installed and set it to point at that.
* Run 'Configure' again, and then 'Generate'.<br />This step creates the ''FlightGear-Meta'' solution (.sln) in C:\FGFS\metabuild  
* Run 'Configure' again, and then 'Generate'.<br />This step creates the ''FlightGear-Meta'' solution (.sln) in C:\FGFS\metabuild  
* Build the FlightGear-Meta solution in C:\FGFS\metabuild<br />
* Build the FlightGear-Meta solution in C:\FGFS\metabuild<br />
: You can build the -Meta solution from a Visual Studio command prompt using msbuild, or open up the .sln in the IDE and again hit build. The first time will be slow - OpenSceneGraph and Boost will be downloaded and compiled, followed by all of simgear and finally flightgear.<br />This step creates ''FlightGear.sln'' in C:\FGFS\metabuild\fgbuild
: You can build the -Meta solution from a Visual Studio command prompt using msbuild, or open up the .sln in the IDE and hit build.<br />To avoid build errors in the IDE, perform your first build using the 'Release' build configuration rather than a 'Debug' configuration. Building in 'Debug' configuration can fail if some release-mode files (such as for OpenSceneGraph) are not already present in their folders.<br />The first time will be slow - OpenSceneGraph and Boost will be downloaded and compiled, followed by all of simgear and finally flightgear.<br />This step creates ''FlightGear.sln'' in C:\FGFS\metabuild\fgbuild


Once the -Meta build completes, you will already have a flyable executable in either C:\FGFS\metabuild\install\msvc100-64\FlightGear\bin or  C:\FGFS\metabuild\install\msvc100\FlightGear\bin depending on whether it's 64 or 32 bit. Other files such as fgrun.exe can be found and copied from the nearby folders under \install if required.
Once the -Meta build completes, you will already have a flyable executable in either C:\FGFS\metabuild\install\msvc100-64\FlightGear\bin or  C:\FGFS\metabuild\install\msvc100\FlightGear\bin depending on whether it's 64 or 32 bit. Other files such as fgrun.exe can be found and copied from the nearby folders under \install if required.
8

edits

Navigation menu