Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

m
m (→‎Description: http://flightgear.org/forums/viewtopic.php?f=22&t=20304#p186647)
Line 2: Line 2:


== Known Pitfalls ==
== Known Pitfalls ==
FlightGear versions <= 3.0 are known to have a cmake build system issue related to NOT automatically reconfiguring the SG/FG sources after updating the version files in in $SG_SRC and $FG_SRC, which basically means that using "git pull" to update your source trees (via the d&c script) will create the latest binaries, but they may not be looking for the right base package data, because the source trees are still using the old version files. This has been encountered by various contributors, including at least one core developer.
FlightGear versions <= 3.0 are known to have a cmake build system issue related to NOT automatically reconfiguring the SG/FG sources after updating the version files in in $SG_SRC and $FG_SRC, which basically means that using "git pull" to update your source trees (via the d&c script) will create the latest binaries, but they may not be looking for the right base package data, because the source trees are still using the old version files found in the cmake cache. This has been encountered by various contributors, including at least one core developer.


To work around this issue, simply switch into your SG/FG build directories and reconfigure each tree by running "cmake ." - for further info, see [http://flightgear.org/forums/viewtopic.php?f=22&t=20304#p186647][http://flightgear.org/forums/viewtopic.php?f=22&p=187413#p186942].
To work around this issue, simply switch to your SG/FG build directories and reconfigure each tree by running "cmake ." - for further info, see [http://flightgear.org/forums/viewtopic.php?f=22&t=20304#p186647][http://flightgear.org/forums/viewtopic.php?f=22&p=187413#p186942].


==Description==
==Description==