Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
OpenRTI switch information and troubleshooting
(→‎Optimus technology: FGRUN run script generation)
(OpenRTI switch information and troubleshooting)
Line 56: Line 56:


At the moment, it's probably safe to say that HLA is only of interest to developers and people willing to play with experimental features.
At the moment, it's probably safe to say that HLA is only of interest to developers and people willing to play with experimental features.
you can pass the '''-i''' option to compile OpenRTI, as well as SimGear and FlightGear re-configured with -D ENABLE_RTI=ON option (experimental)


==== When building Next you may see build errors ====
==== When building Next you may see build errors ====
Line 173: Line 175:


Sometimes it happens that the script fails to compile only fgrun, fgcom or atlas, if you then see the run_fgfs.sh file it means that FlightGear installation was successful and you can safely run it.
Sometimes it happens that the script fails to compile only fgrun, fgcom or atlas, if you then see the run_fgfs.sh file it means that FlightGear installation was successful and you can safely run it.
=== OpenRTI undefined reference errors ===
Sometimes due to the way d&c build cleans up projects, linking errors might occur, this is the case with this error "libRTI-NG.so: undefined reference to xxx", sadly at this point either you need to patch the d&c script to clean OpenRTI with rm -f CMakeCache.txt && rm -rf CMakeFiles/, or just start from a clean environment, assuming you are in the parent project directory, you will need to issue this command to clean everything(except FGDATA):
<pre>
rm -rf build/* install/simgear/ install/openrti/ install/flightgear/share/ install/flightgear/bin/
</pre>
see this thread for more details(http://forum.flightgear.org/viewtopic.php?f=45&t=26244)


== Options ==
== Options ==
272

edits

Navigation menu