Talk:Building FlightGear - Cross Compiling: Difference between revisions

Jump to navigation Jump to search
m
Line 57: Line 57:


: having a prototype (for SimGear headless) would make sense in my opinion, and it coud be used as a template for other (non-headless) stuff, including both, SG & FG as a whole, but also other dependencies (think openrti). So given that SimGear is the only common dependency here, I would suggest to prototype a well-commented example and get this committed, so that others can take a look and learn from it, e.g. to help refine SG/FG support and come up with modules for optional dependencies. The [[Superbuild]] would be a different beast anyway, because it is trying to do everything (including the source check outs), so that would require some thinking - and having experience with dedicated simgear.mk and flightgear.mk files should come in very handy for that.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:47, 28 May 2015 (EDT)
: having a prototype (for SimGear headless) would make sense in my opinion, and it coud be used as a template for other (non-headless) stuff, including both, SG & FG as a whole, but also other dependencies (think openrti). So given that SimGear is the only common dependency here, I would suggest to prototype a well-commented example and get this committed, so that others can take a look and learn from it, e.g. to help refine SG/FG support and come up with modules for optional dependencies. The [[Superbuild]] would be a different beast anyway, because it is trying to do everything (including the source check outs), so that would require some thinking - and having experience with dedicated simgear.mk and flightgear.mk files should come in very handy for that.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:47, 28 May 2015 (EDT)
== Superbuild ==
This isn't relevant at the moment, but referring to the Superbuild related comments above: it seems we could end up with a viable workaround by figuring out if/how and where those *.mk files are getting the value for <nowiki>-DCMAKE_TOOLCHAIN_FILE='$(CMAKE_TOOLCHAIN_FILE)'</nowiki> from - i.e. '''CMAKE_TOOLCHAIN_FILE''' specifically, and directly reuse that in the Superbuild (need to check if that'd work). But if it's too much of a hassle, let's just focus on *.mk files for starters. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:06, 28 May 2015 (EDT)


== .deb packaging ==
== .deb packaging ==

Navigation menu