20,741
edits
Building FlightGear - Cross Compiling: Difference between revisions
Jump to navigation
Jump to search
m
→Goals
m (→Goals) |
m (→Goals) |
||
| Line 23: | Line 23: | ||
Allow Linux-based contributors to easily provide customized FlightGear binaries to Windows-based users by cross-compiling FlightGear and all its dependencies (OpenSceneGraph, PLIB, OpenAL, SimGear etc), including support for the new osgEarth mode, developed by poweroftwo. | Allow Linux-based contributors to easily provide customized FlightGear binaries to Windows-based users by cross-compiling FlightGear and all its dependencies (OpenSceneGraph, PLIB, OpenAL, SimGear etc), including support for the new osgEarth mode, developed by poweroftwo. | ||
In addition, one challenge frequently encountered on the FlightGear forums is that release candidates usually get very little, if any, thorough testing and that Windows-based end-users form the largest share of our users, but most of them are unable to provide action-able bug reports, e.g. due to being unable to provide backtraces or running diagnostic tools like valgrind, google perftools etc | In addition, one challenge frequently encountered on the FlightGear forums is that RCs (release candidates) usually get very little, if any, thorough testing by end users and that Windows-based end-users form the largest share of our users, but most of them are unable to provide action-able bug reports, e.g. due to being unable to provide backtraces or running/using diagnostic tools like gdb, valgrind, google perftools etc. | ||
Given the focus on creating binaries specifically for Windows, we are also investigating options for patching FlightGear to provide better diagnostic tools if necessary, especially invovling Google BreakPad for providing backtraces: | This is also an issue identified by other developers (e.g. TerraGear). And it was one of the original reasons for integrating support for [[CrashRpt]]. | ||
Given the focus on creating binaries specifically for Windows end-users, we are also investigating options for patching FlightGear to provide better diagnostic tools if necessary, especially invovling Google BreakPad for providing backtraces: | |||
{{FGCquote | {{FGCquote | ||