20,741
edits
FlightGear 3.0 backlog: Difference between revisions
Jump to navigation
Jump to search
m
→Misc
m (→Eye Candy) |
m (→Misc) |
||
| Line 55: | Line 55: | ||
Let me be the first to admit that it's much more fun doing my own stuff the way I like and then just merge it in. But if we can find consensus about any plan having to do with integration of new features and making it all work together, then I'm willing to reserve the majority of my coding time for working towards that goal. Would this be something to aim for in a 3.0 release? | Let me be the first to admit that it's much more fun doing my own stuff the way I like and then just merge it in. But if we can find consensus about any plan having to do with integration of new features and making it all work together, then I'm willing to reserve the majority of my coding time for working towards that goal. Would this be something to aim for in a 3.0 release? | ||
== CMake Build System Issue == | |||
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. | |||
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]. | |||
=== Misc === | === Misc === | ||