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 00:16, 30 May 2015
, 30 May 2015→Superbuild
Hamzaalloush (talk | contribs) |
Hamzaalloush (talk | contribs) |
||
| Line 107: | Line 107: | ||
: even "just" *.mk based cross compilation would be useful already - however, it would obviously be platform specific, while the Superbuild is pretty much guaranteed to stay around, and to be maintained in the future - i.e. due to it not being specific to any single platform/os or compiler, and due to it being used by the Jenkins build server. All the dependencies would still need to build/work correctly - so I guess it would be more difficult to use/adapt the Superbuild directly. Once mxe is able to build FG and all deps using *.mk files, we should strive to review all necessary additions/patches and try to get those merged upstream (mxe, sg, fg etc) - the Superbuild would be nice to support because that would mean that mxe-based cross compilation would be handled by the same front-end. But even just having a handful of *.mk files would be very useful, i.e. to provide FG/osgEarth binaries to Windows-based end users.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:35, 29 May 2015 (EDT) | : even "just" *.mk based cross compilation would be useful already - however, it would obviously be platform specific, while the Superbuild is pretty much guaranteed to stay around, and to be maintained in the future - i.e. due to it not being specific to any single platform/os or compiler, and due to it being used by the Jenkins build server. All the dependencies would still need to build/work correctly - so I guess it would be more difficult to use/adapt the Superbuild directly. Once mxe is able to build FG and all deps using *.mk files, we should strive to review all necessary additions/patches and try to get those merged upstream (mxe, sg, fg etc) - the Superbuild would be nice to support because that would mean that mxe-based cross compilation would be handled by the same front-end. But even just having a handful of *.mk files would be very useful, i.e. to provide FG/osgEarth binaries to Windows-based end users.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:35, 29 May 2015 (EDT) | ||
:: which is exactly why we started this whole initiative, to provide osgEarth binaries first and foremost. now, on the subject of getting these package changes reviewed and merged into upstream/master... i don't think that's realistic, given that i did my own thing to make it work *on my distribution*, so as it stands, for the sake of progress, we should focus on our branch, it's very clear to see how each plugin/dependancy was built from .mk files to check for regressions, my branch is so off the fork it's not even funny, converting some packages to CMake and reverting to stable GCC among others. -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 20:16, 29 May 2015 (EDT) | |||
== .deb packaging == | == .deb packaging == | ||