20,741
edits
Post FlightGear 2020.2 LTS changes: Difference between revisions
Jump to navigation
Jump to search
m
Post FlightGear 2020.2 LTS changes (view source)
Revision as of 17:49, 25 August 2020
, 25 August 2020→Current status: https://sourceforge.net/p/flightgear/mailman/message/37091728/
m (→Code clean-ups and changes: https://sourceforge.net/p/flightgear/mailman/message/37091728/) |
m (→Current status: https://sourceforge.net/p/flightgear/mailman/message/37091728/) |
||
| Line 1: | Line 1: | ||
== Current status == | == Current status == | ||
{{Mergeto|Building using CMake}} | |||
'''06/2020''': | '''06/2020''': | ||
| Line 15: | Line 17: | ||
Let’s see if reality corresponds to all the theory above :)<ref>https://sourceforge.net/p/flightgear/mailman/message/37041064/</ref> | Let’s see if reality corresponds to all the theory above :)<ref>https://sourceforge.net/p/flightgear/mailman/message/37041064/</ref> | ||
'''08/2020''': | |||
James pushed a large overhaul of the Cmake build files for FlightGear: | |||
* we now use modern Cmake style nearly everywhere, i.e targets-as-objects for an OOP-style build system | |||
* transitive dependencies are handled automatically (or at least, that’s the idea…), which simplifies things in many places (eg, audio library handling) | |||
* system vs built-in dependencies is handled vis ALIAS targets, so most other code doesn’t care. We link to a target which is an alias for either our built-in version or the system one (via an IMPORTED target) | |||
* we should have better isolation from system headers / versions of things. <ref>https://sourceforge.net/p/flightgear/mailman/message/37091728/</ref> | |||
== Changes that are already on next == | == Changes that are already on next == | ||