20,741
edits
m (→MXE central repository: split off separate topics) |
|||
Line 158: | Line 158: | ||
: right, for now, I guess it makes sense to agree on a single repo, and add volunteers/contributors as committers - while asking people to help maintain the wiki article, so that others can more easily follow everything. I don't have any preference regarding which repo to use, so I trust your judgement. Besides, how long does it take for you to build everything ? Should we already look around for compile farm/OBS access (those systems typically having at least ~12 cores and ~32gb of RAM) ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:35, 30 May 2015 (EDT) | : right, for now, I guess it makes sense to agree on a single repo, and add volunteers/contributors as committers - while asking people to help maintain the wiki article, so that others can more easily follow everything. I don't have any preference regarding which repo to use, so I trust your judgement. Besides, how long does it take for you to build everything ? Should we already look around for compile farm/OBS access (those systems typically having at least ~12 cores and ~32gb of RAM) ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:35, 30 May 2015 (EDT) | ||
:: i'm ready to remove my repository and base my work on Flyhigh's if he's ok, we are already done with FG, the mk files are there. even if not (seg-fault free). {{usr|Flyhigh}} gonna have to report if it was by C++11 compilation(else might be core issue). | :: i'm ready to remove my repository and base my work on Flyhigh's if he's ok, we are already done with FG, the mk files are there. even if not (seg-fault free). {{usr|Flyhigh}} gonna have to report if it was by C++11 compilation(else might be core issue) [...] -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 14:51, 30 May 2015 (EDT) | ||
: ok, sounds like a plan --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:06, 30 May 2015 (EDT) | |||
: | == ccache & distcc == | ||
as for the other question, it takes about 2 hours on an i5. we can look to the compile farm when doing testing other distribution i guess. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 14:51, 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 == | |||
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) |