272
edits
Talk:Building FlightGear - Cross Compiling: Difference between revisions
Jump to navigation
Jump to search
Talk:Building FlightGear - Cross Compiling (view source)
Revision as of 16:33, 6 June 2015
, 6 June 2015→Status 06/2015 ?: segfaults
Hamzaalloush (talk | contribs) |
Hamzaalloush (talk | contribs) (→Status 06/2015 ?: segfaults) |
||
| Line 193: | Line 193: | ||
:Haven't gotten anywhere on the crash with i686 shared, so I'm working on the static side of things and also slowly upstreaming our changes here. Also, 64-bit is starting to be painful (mainly because of portablexdr). I'm now building i686 static and hoping that that at least builds. -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 11:42, 6 June 2015 (EDT) | :Haven't gotten anywhere on the crash with i686 shared, so I'm working on the static side of things and also slowly upstreaming our changes here. Also, 64-bit is starting to be painful (mainly because of portablexdr). I'm now building i686 static and hoping that that at least builds. -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 11:42, 6 June 2015 (EDT) | ||
::perhaps the segfaults are related to using 32-bit cinaries with the new WS/2.0 scenery?? just an idea -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 12:33, 6 June 2015 (EDT) | |||
:: is there any way to share the broken stuff so that we can take a look - i.e. how about committing broken stuff to a separate topic branch, so that people can more easily follow what is going on and help find a solution ? Alternatively, let's exchange the corresponing logs on the wiki. Obviously, it would help to know if any of the build/run-time issues are affected by type of build and/or the target/library built. My suggestion would be to start with self-contained tests/demos unrelaeted to FG, and maybe switch to running FG/SG unit tests afterwards ?--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:49, 6 June 2015 (EDT) | :: is there any way to share the broken stuff so that we can take a look - i.e. how about committing broken stuff to a separate topic branch, so that people can more easily follow what is going on and help find a solution ? Alternatively, let's exchange the corresponing logs on the wiki. Obviously, it would help to know if any of the build/run-time issues are affected by type of build and/or the target/library built. My suggestion would be to start with self-contained tests/demos unrelaeted to FG, and maybe switch to running FG/SG unit tests afterwards ?--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:49, 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) | |||