These changes are the small bits needed to allow us to build an OSX dmg from Linux, with no OSX environment needed. They should be completely noninvasive to current builds, but some verification would be much appreciated.
The dependencies are here for now: https://github.com/theuni/osx-cross-depends
While this may not be immediately useful for 0.9.0, it would be nice to have the final release build-able this way, so that we can compare apples/apples when discussing its use in the future.
678 | @@ -671,6 +679,7 @@ if test "x$use_tests$build_bitcoind$use_qt" = "xnonono"; then 679 | fi 680 | 681 | AM_CONDITIONAL([TARGET_DARWIN], [test x$TARGET_OS = xdarwin]) 682 | +AM_CONDITIONAL([BUILD_APPLE], [test x$BUILD_OS = xapple])
Any reason not to use _DARWIN instead of _APPLE? (so we'd have BUILD_DARWIN and TARGET_DARWIN)
The conditionals match the values we receive for host/build. After a second look, I agree. We should be using build_os rather than build_vendor, in which case we'll match against darwin like the host test.
I'll push up a fix.
ACK
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/2d472231f958944f6602cf82b8fe7c0b5f091142 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
These come from the enironment, which will be properly setup by Make with
the paths gleaned from configure.
Also don't crash if plugins are static.
For qt5.2 on osx, the qcocoa plugin is mandatory. However, it fails to load
when qt.conf specifies the "plugin" path instead of the expected "Plugin". This
is in line with the documentation:
https://qt-project.org/doc/qt-5.0/qtdoc/qt-conf.html
I'm not sure how the plugins were loading before, unless the case-sensitivity
for OSX is new.
This should be safe to do for native builds too, but for now it's
specific to cross-builds to avoid possible regressions.