272
edits
Building FlightGear - Cross Compiling: Difference between revisions
Jump to navigation
Jump to search
m
→TerraGear
Hamzaalloush (talk | contribs) m (→Gallery) |
Hamzaalloush (talk | contribs) m (→TerraGear) |
||
| Line 818: | Line 818: | ||
* As request for custom scenery generation arises among end-users/data developers, we see the need for a cross-platform ready set of tools handy. since then the effort started for providing Terragear on Windows(initially by {{usr|Hamzaalloush}}). It was expected that Terragear, as a scenery generation tool, that was made to deployed on a Linux server, would have portability problems. this effort would at least pinpoint issues with portability for the underlying structure of FlightGear. | * As request for custom scenery generation arises among end-users/data developers, we see the need for a cross-platform ready set of tools handy. since then the effort started for providing Terragear on Windows(initially by {{usr|Hamzaalloush}}). It was expected that Terragear, as a scenery generation tool, that was made to deployed on a Linux server, would have portability problems. this effort would at least pinpoint issues with portability for the underlying structure of FlightGear. | ||
* The Terragear tools for scenery generation would be the ideal environment on which to bring"Small, stable, incremental changes which are preferable to larger monolithic changes | * The Terragear tools for scenery generation would be the ideal environment on which to bring "Small, stable, incremental changes which are preferable to larger monolithic changes for ease of review", adhering to the FG roadmap for development, since we are mainly dealing with the basic building blocks for Flightgear, where a Simgear based environment is the only prerequisite. the SG abstraction layer for threading, as well as for maths are good points to investigate in this setup(as it is used throughly), as well as providing small patches upstream towards getting Simgear, Mingw64 compatible as the end-goal. | ||
* The relatively smaller number of static symbols collected from such an effort, is a good basis for investigating debugging facilities on cross-compiled binaries. | * The relatively smaller number of static symbols collected from such an effort, is a good basis for investigating debugging facilities on cross-compiled binaries. | ||