Post FlightGear 2020.2 LTS changes: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (Johan G moved page Post LTS Changes to Post FlightGear 2020.2 LTS Changes: Less ambiguous tilte)
m (+cat: Core development)
Line 20: Line 20:
* Remove the 2D panel code in favour of Canvas (this requires completing some work to load 2D panel elements as Canvas, from XML)
* Remove the 2D panel code in favour of Canvas (this requires completing some work to load 2D panel elements as Canvas, from XML)
* Remove the C++ HUD in favour of Canvas-based version : this requires some kind of migration script or framework, so we have at least the default UFO HUD available
* Remove the C++ HUD in favour of Canvas-based version : this requires some kind of migration script or framework, so we have at least the default UFO HUD available
[[Category:Core development]]

Revision as of 15:32, 27 April 2020

Post 2020.2 LTS code clean-ups and changes

Collecting what's going to change : this will also be used to work out what manual or automatic migrations are required to keep aircraft working. It's expected that for the first few months of 'next', there will be higher than usual breakage, i.e regular might not be possible.

As a general guideline, the minimum system to develop / build the code on will be Ubuntu 18.04 LTS (Bionic) : the versions below correspond to what is available in a stock Bionic install.

  1. Make C++14 the minimum required version (will make it easier to continue replacing Boost items with std:: ones)
  2. Make CMake 3.6 the minimum required version : this will allow simplifying a bunch of compatibility logic in the build files
  3. Make Qt 5.9 the minimum for the launcher
  4. Drop 32-bit windows support
  5. Drop the pre-2017.x MultiPlayer message format - this will fix warnings from some aircraft about MP packet overflows
  6. Drop the KLN-89 code, since it's unused and not maintained for a long time: Canvas and the regular GPS code can easily implement a working KLN-89 or similar equipment now
  7. Switch to Compositor mode as the only rendering option
  8. Drop Rembrandt support from C++ (really part of the above)
  9. Drop the non-ALS shaders / pipeline : this will reduce the number of options to test in the compositor effects
  10. Drop the C++ NavDisplay : the Canvas version replaces it

Possible additional items

  • Remove the 2D panel code in favour of Canvas (this requires completing some work to load 2D panel elements as Canvas, from XML)
  • Remove the C++ HUD in favour of Canvas-based version : this requires some kind of migration script or framework, so we have at least the default UFO HUD available