Mac OS X UpdateFinally it's here! I've been testing it on Mac OS X 10.7.5 with both I2P enabled and not. Working fine for me. Please report any errors!
You Mac OS X users are also the lucky first to use the new codebase, 0.8.3.7
http://anoncoin.net/downloads/Anoncoin-Qt.dmgRelease for windows will be out within some days. First we'll add coin control! We will update the Mac OS X client as well with that new feature. Linux users are free to compile! - We're also planning to release Linux binaries, but no schedule there.
Thank you for this!
however its not working, still getting
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /opt/local/lib/libcrypto.1.0.0.dylib
Referenced from: /Applications/Anoncoin-Qt.app/Contents/Frameworks/libssl.1.0.0.dylib
Reason: image not found
so it sounds like its on my end. Does Xcode need to be installed?
Hmm.. This was odd. I'd checked the binaries now.
$ ls Anoncoin-Qt.app/Contents/Frameworks/
QtCore.framework libboost_program_options.dylib
QtGui.framework libboost_system-mt.dylib
QtNetwork.framework libboost_system.dylib
libQtCore.dylib libboost_thread-mt.dylib
libQtGui.dylib libboost_thread.dylib
libQtNetwork.dylib libcrypto.1.0.0.dylib
libboost_chrono-mt.dylib libdb_cxx-4.8.dylib
libboost_chrono.dylib libminiupnpc.8.dylib
libboost_filesystem-mt.dylib libpng15.15.dylib
libboost_filesystem.dylib libssl.1.0.0.dylib
libboost_program_options-mt.dylib libz.1.dylib
Files are there..
$ otool -L Anoncoin-Qt.app/Contents/MacOS/A
Anoncoin-Qt.app/Contents/MacOS/Anoncoin-Qt:
@executable_path/../Frameworks/libminiupnpc.8.dylib (compatibility version 0.0.0, current version 0.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 833.25.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 41.0.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1138.51.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 53.0.0)
@executable_path/../Frameworks/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/libdb_cxx-4.8.dylib (compatibility version 0.0.0, current version 0.0.0)
@executable_path/../Frameworks/libboost_system.dylib (compatibility version 0.0.0, current version 0.0.0)
@executable_path/../Frameworks/libboost_filesystem.dylib (compatibility version 0.0.0, current version 0.0.0)
@executable_path/../Frameworks/libboost_program_options.dylib (compatibility version 0.0.0, current version 0.0.0)
@executable_path/../Frameworks/libboost_thread.dylib (compatibility version 0.0.0, current version 0.0.0)
@executable_path/../Frameworks/libboost_chrono.dylib (compatibility version 0.0.0, current version 0.0.0)
@executable_path/../Frameworks/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.5)
@executable_path/../Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.5)
@executable_path/../Frameworks/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.8.0, current version 4.8.5)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 635.21.0)
Linking seems fine too..
It was built using macports with custom options. So I guess macports then, which requires Xtools. Source:
http://gavintech.blogspot.no/2011/11/deploying-bitcoin-qt-on-osx.htmlBut it should be possible to make a version not requiring macports. I will research it more! Thanks for the detailed report!