Talk:Building FlightGear - Cross Compiling: Difference between revisions

Jump to navigation Jump to search
m
Line 199: Line 199:


:I'm now on i686-w64-mingw32.static, trying to build terragear all of a sudden. got some commits up on a new master-oldgcc-terragear branch containing patches for geos(fix exported symbols), boost(force static), and a terragear.mk with mingw specific patches that makes it compile 90% of the way. for last status updates overall, {{usr|Flyhigh}} seems to interact pretty well the MXE community and got some changes commited to upstream[https://github.com/mxe/mxe/pull/698][https://github.com/mxe/mxe/pull/699]. i agree with the compile log's idea, let us make another topic for that, as long as we keep them even if solved for later reference. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 12:21, 6 June 2015 (EDT)
:I'm now on i686-w64-mingw32.static, trying to build terragear all of a sudden. got some commits up on a new master-oldgcc-terragear branch containing patches for geos(fix exported symbols), boost(force static), and a terragear.mk with mingw specific patches that makes it compile 90% of the way. for last status updates overall, {{usr|Flyhigh}} seems to interact pretty well the MXE community and got some changes commited to upstream[https://github.com/mxe/mxe/pull/698][https://github.com/mxe/mxe/pull/699]. i agree with the compile log's idea, let us make another topic for that, as long as we keep them even if solved for later reference. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 12:21, 6 June 2015 (EDT)
:: Thank you for trying to get useful things merged upstream - regarding those crashes, if you can, please share your gdb backtraces using either the wiki or some form of pastebin. If that is not an option, I would suggest to prioritize working out a useful way to add better debugging support for those binaries (e.g. using Breakpad) so that we don't need to use gdb for getting a backtrace. Regarding PortableXDR: where is that being used currently, would it make sense to reuse the tinyXDR implementation in SG/FG (mp) or at least look at it for reference/patching ? If you think those segfaults may be scenery related, I would suggest to consider using the minimal startup profile to check that theory, i.e. by excluding scenery from being loaded altogether. Trying to build TG seems like another useful test case, so maybe we should add  this to the roadmap, because it will pull in tons of other SG/FG dependencies. For troubleshooting segfaults, I would suggest to focus first on simple binaries, e.g. unit tests in SimGear and/or $FG_SRC/utils (e.g. stuff like fgviewer, fgjs etc). Maybe we could update the wiki to present a more up to date list of recent developments and/or required work that lies ahead of us ?--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:33, 6 June 2015 (EDT)

Navigation menu