20,741
edits
Talk:Building FlightGear - Cross Compiling: Difference between revisions
Jump to navigation
Jump to search
m
Talk:Building FlightGear - Cross Compiling (view source)
Revision as of 19:07, 30 May 2015
, 30 May 2015merge related sections
m (→MXE central repository: split off separate topics) |
m (merge related sections) |
||
| Line 142: | Line 142: | ||
:: yup, you can clone this from my branch and get it going with only 'git clone -b master-oldgcc https://github.com/hamzaalloush/mxe-clone.git' && 'make openscenegraph', but i do not guarantee all packages will be working on non-Ubuntu system. i have a back-up rig that has Debian Wheezy in it, and was unable to compile with it. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 16:50, 28 May 2015 (EDT) | :: yup, you can clone this from my branch and get it going with only 'git clone -b master-oldgcc https://github.com/hamzaalloush/mxe-clone.git' && 'make openscenegraph', but i do not guarantee all packages will be working on non-Ubuntu system. i have a back-up rig that has Debian Wheezy in it, and was unable to compile with it. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 16:50, 28 May 2015 (EDT) | ||
== Reported Segfaults == | == Reported Segfaults == | ||
| Line 166: | Line 160: | ||
btw, on a single computer you can use ccache to cache previously compiled object files (which will take up several gb of disk space), if you have access to other computers on the LAN, you can also use distcc (possibly in conjunction with ccache). For me, using just ccache helps speed up OSG/SG/FG compilation significantly, because most files are unlikely to have been modified at all - so can usually be reused "as is". --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:03, 30 May 2015 (EDT) | btw, on a single computer you can use ccache to cache previously compiled object files (which will take up several gb of disk space), if you have access to other computers on the LAN, you can also use distcc (possibly in conjunction with ccache). For me, using just ccache helps speed up OSG/SG/FG compilation significantly, because most files are unlikely to have been modified at all - so can usually be reused "as is". --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:03, 30 May 2015 (EDT) | ||
== osgEarth == | == OSG & osgEarth == | ||
Given that OSG now builds correctly, I would suggest to come up with a dedicated <code>osgearth.mk</code> file for testing purposes, which we can also use as a template for SG/FG <code>flightgear-osgearth.mk</code> afterwards, while also preparing support for the osgearth branch poweroftwo has been maintaining. In addition, osgearth comes with a bunch of osgearth applications that should be useful for testing purposes (OSG vs. osgearth support, both being required for linking) --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 00:32, 29 May 2015 (EDT) | |||
: good post-coffee (+3 GMT) afternoon :) sure, i'll look into that since {{usr|Flyhigh}} is unto the sf/fg mk files for now. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 04:25, 29 May 2015 (EDT) | |||
it remains for me to make the osg-earth.mk(have some undefined references right now), than to get FG/SG with osgearth-patch. see [https://gitlab.com/poweroftwo/flightgear-osgearth], that'll be a matter of download and compile only as poweroftwo has rebased his work on release/3.4, and that's already working for us now. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 14:51, 30 May 2015 (EDT) | it remains for me to make the osg-earth.mk(have some undefined references right now), than to get FG/SG with osgearth-patch. see [https://gitlab.com/poweroftwo/flightgear-osgearth], that'll be a matter of download and compile only as poweroftwo has rebased his work on release/3.4, and that's already working for us now. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 14:51, 30 May 2015 (EDT) | ||