Drop support for 32-bit or pre-10.6 Macs.
Also, some of the OSX build docs hadn't been updated since the autotools change.
Drop support for 32-bit or pre-10.6 Macs.
Also, some of the OSX build docs hadn't been updated since the autotools change.
Drop support for 32-bit or pre-10.6 Macs.
Also, some of the OSX build docs hadn't been updated since the
autotools change.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/26e4b52712faf8e60814f7f6030b6dded1df8038 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.
47 | @@ -47,6 +48,10 @@ Installing the dependencies using MacPorts is very straightforward. 48 | 49 | sudo port install boost db48@+no_java openssl miniupnpc autoconf pkgconfig automake 50 | 51 | +Optional: install Qt4 52 | + 53 | + sudo port install qt4-mac qrencode protobuf-cpp
It'd be preferable to use Qt 5.2 on Mac instead of Qt 4, as it fixes the high-dpi display blurriness.
I need somebody to tell me the magic incantation to either:
Yes using Qt5 as frameworks was tricky. I remember someone on IRC was doing that. It is a matter of making sure that the configure script can find the pkg-tool .pc files. But he also had to edit the .pc files to fix the include path, as somehow that was wrong in the framework release.