Deboosting FlightGear: Difference between revisions

Jump to navigation Jump to search
(placeholder ...)
 
Line 9: Line 9:
We can’t drop it, without some nasty work : Gaétan has removed a lot of pieces, but the remaining items are going to be more of a battle (and there’s one or two we might need to fork or find a different solution), especially the ‘bimap’ used in the Effects code)
We can’t drop it, without some nasty work : Gaétan has removed a lot of pieces, but the remaining items are going to be more of a battle (and there’s one or two we might need to fork or find a different solution), especially the ‘bimap’ used in the Effects code)


Of course, patches always welcome, but untangling Boost from especially the Nasal-cppbind code needs some fairy dedicated meta-programming work :) The good news is if it compiles, it’s probably going to work. (Don’t ask about the bad news…)
Of course, patches always welcome, but untangling Boost from especially the [[Nasal/CppBind|Nasal-cppbind code]] needs some fairy dedicated meta-programming work :) The good news is if it compiles, it’s probably going to work. (Don’t ask about the bad news…)


This is a reason to move to C++14 after the LTS branches : a bunch more stuff will become available to us in the standard lib, replacing Boost-isms. The catch is we need t keep the LTS building with new Boost versions, so we can’t avoid some issues like you encountered.<ref>https://sourceforge.net/p/flightgear/mailman/message/37021826/</ref>
This is a reason to move to C++14 after the LTS branches : a bunch more stuff will become available to us in the standard lib, replacing Boost-isms. The catch is we need t keep the LTS building with new Boost versions, so we can’t avoid some issues like you encountered.<ref>https://sourceforge.net/p/flightgear/mailman/message/37021826/</ref>

Navigation menu