Superbuild: Difference between revisions

Jump to navigation Jump to search
Line 43: Line 43:


: 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 />
: 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.


It is easier to run FlightGear by closing the -Meta solution, and instead opening the FlightGear.sln in C:\FGFS\metabuild\fgbuild. From here you can set 'fgfs' as the startup project, enter any command line options, and debug / hack / run the code as normal.
<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.<br />


Note you will need to add the OpenSceneGraph install directory to the PATH variables in the 'fgfs' target properties; the dir will be something like C:\FGFS\metabuild\install\msvc100\OpenSceneGraph\bin. Again this step will hopefully go away soon, but for the moment is still required.
<br />It is easier to run FlightGear by closing the -Meta solution, and instead opening the FlightGear.sln in C:\FGFS\metabuild\fgbuild. From here you can set 'fgfs' as the startup project, enter any command line options, and debug / hack / run the code as normal.
 
Note you will need to add the OpenSceneGraph install directory to the PATH variables in the 'fgfs' target properties; the dir will be something like C:\FGFS\metabuild\install\msvc100\OpenSceneGraph\bin. Again this step will hopefully go away soon, but for the moment is still required.
 
[03/2014 note re "CrashRpt setup failed" / "Missing language file or wrong language file version" when running a 64-bit executable.
<br />It happens because the file ''crashrpt_lang.ini'' is missing from the \bin folder.  This in turn is because it is missing from the original 3rdparty dependencies download source used by SuperBuild. The 32-bit build does not have this issue because the 32-bit download source does contain the file.  One workaround is to simply copy the ''crashrpt_lang.ini'' file from a 32-bit installation if you have one. Alternatively, you can obtain it directly from the 32 bit download source SuperBuild uses, which currently is at "http://fgfs.goneabitbursar.com/fgwin3rdparty/trunk/msvc100/" (you can double-check that inside C:\FGFS\fgmeta\CMakeLists.txt by searching for the "ExternalProject_Add" setting for "WinDeps").]<br />


Using other generators / IDEs: untested, but quite likely to work if they already work with CMake. Try it out.
Using other generators / IDEs: untested, but quite likely to work if they already work with CMake. Try it out.
8

edits

Navigation menu