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 20:44, 28 May 2015
, 28 May 2015no edit summary
Hamzaalloush (talk | contribs) (simgear.mk/fgfs.mk & .deb packaging) |
mNo edit summary |
||
| Line 57: | Line 57: | ||
what should the .deb package consist of? a freeze of a successful build with all it's packages? it's totaling 3 GB's right now on my system. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 16:35, 28 May 2015 (EDT) | what should the .deb package consist of? a freeze of a successful build with all it's packages? it's totaling 3 GB's right now on my system. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 16:35, 28 May 2015 (EDT) | ||
: right, I guess we do have different target audiences: those just wanting to cross-compile FG (without all the setup overhead) would definitely benefit most from everything pre-compiled included, so I would suggest to keep things simple for now and just turn the whole shebang into a deb/ppa package to ensure that FG (including all deps) can be built. I can also help and turn this into a virtual appliance for VirtualBox (possibly including a working fg source tree) But I think we only need to look into this once the other items can be scratched off from the roadmap - i.e. once SG/FG actually build & link correctly. In the meantime, it should probably be safe to assume that all parties interested in this, are able to get/set up and use mxe from your github branch ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:44, 28 May 2015 (EDT) | |||