20,741
edits
Building FlightGear - Cross Compiling: Difference between revisions
Jump to navigation
Jump to search
m
Building FlightGear - Cross Compiling (view source)
Revision as of 12:37, 31 October 2015
, 31 October 2015→Dependencies: Qt5 comments (pm2wiki)
m (→News: status updates) |
m (→Dependencies: Qt5 comments (pm2wiki)) |
||
| Line 69: | Line 69: | ||
This is a list of dependencies (usually, dedicated *.mk modules for mxe) | This is a list of dependencies (usually, dedicated *.mk modules for mxe) | ||
{{Note|All main dependencies (osg,osgearth, simgear, flightgear) will by default be built using <nowiki>-DCMAKE_BUILD_TYPE=DEBUG</nowiki> to ensure that we can easily troubleshoot problems, once all unit tests (demos/examples) of each package build/link and work correctly, the build type for the corresponding package will be promoted to '''RelWithDbg'''.}} | {{Note|All main dependencies (osg,osgearth, simgear, flightgear) will by default be built using <nowiki>-DCMAKE_BUILD_TYPE=DEBUG</nowiki> to ensure that we can easily troubleshoot problems, once all unit tests (demos/examples) of each package build/link and work correctly, the build type for the corresponding package will be promoted to '''RelWithDbg'''. | ||
Also, Qt 5 is in MXE, but because the source code has been split into multiple source packages, the "qt5" target just builds all of the Qt 5 components. For Flightgear, I think "qtbase" (and "qtdeclarative", if it uses QML files) is sufficient. | |||
Since Qt5 is an optional dependency for a launcher, we will not focus on something that could be achieved equally using another launcher, the purpose of our MXE adventure is to help people troubleshoot and compile faster than nightly without going Windows SDK, but it is definitely "nice-to-have" the QT launcher, so that will have to wait. | |||
}} | |||
{| class="wikitable" | {| class="wikitable" | ||