Superbuild: Difference between revisions

Jump to navigation Jump to search
Line 38: Line 38:
* 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 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
:This build step creates ''FlightGear.sln'' in C:\FGFS\metabuild\fgbuild<br />


: 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 />If the build fails due to a "hash mismatch" in the OpenSceneGraph file, it could be because the source site itself is inaccessible or having temporary issues. To confirm this, check the presence and size of the downloaded OpenSceneGraph-x.x.x.zip file in C:\FGFS\metabuild\src . You might also try and obtain the file directly. To determine where SuperBuild is trying to get the file from, look for the OSG_SOURCE setting defined in C:\FGFS\fgmeta\CMakeLists.txt <br />
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