Armory definitely works for me on 10.12.2. Just sent and received coins today, actually.
That said, can you do me a favor? Go to /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ and edit ArmoryUtils.py at Line 1267. Once saved, start Armory and see if it finishes starting up.
Old:
LOGINFO(' Preferred Encoding : ' + locale.getpreferredencoding())
New:
prefEnc = locale.getpreferredencoding()
if prefEnc == None:
if os.environ.get('LC_ALL', '').upper() == 'UTF-8':
prefEnc = 'utf-8'
else:
prefEnc = 'Unknown'
LOGINFO(' Preferred Encoding : ' + prefEnc)
EDIT: Added a suggested fix.
That worked! Feel free to PR to goatpig. Thanks mate.
Glad to hear it! Will PR ASAP.
droak was the OSX maintainer at ATI. He provides me with the builds (I debug the code through a SSH instance on his machine). I fully trust him, for what it's worth.
As for OSX support in general, I simply do not own a Mac, and it is apparently a mess to get OSX going in a VM. ATI had a full time employee, qualified and available to this task (droark). Being alone and without revenue, supporting OSX is a tough requirement for me. If droark didn't volunteer, I would have had to drop OSX support.
My long term plan is to break down the code base in sub modules and at least enable deterministic builds for mission critical libraries. But for now, this is all I've got.
Yeah, I still do the Mac builds. Here's my build process.
- Run the latest version of VMware Fusion (currently 8.5.3).
- Fire up a VM with OSX 10.11.6 and the latest version of XCode 7 (can't remember the number offhand). This is due to some issues that can't be resolved on my main box until Armory requires OSX 10.8 as a minimum. (10.7 is still the minimum version we support, although I'm pressing for a bump to 10.8 once SegWit and the new wallet are ready.)
- Use Git to pull down the latest code.
- Do a full, clean build.
- Send the resultant .tar.gz file and its SHA256 sum to goatpig.
Believe me, I know this isn't ideal! At ATI, we were working on a Core-like system where cross-compiles were feasible, thereby making deterministic compiles feasible. We even had cross-compiles running internally. The Mac builds did run, albeit with bugs that I never got a chance to fix. It never came out because reasons. It's not possible to lift the code we had because reasons. It's still my goal, and goatpig's, to get a deterministic build system going. It's just going to take awhile because we're both busy, and this isn't something you can rush. If somebody wants to coordinate with goatpig and do a "clean room" solution, I'm more than happy to review your work. (While far from an expert, I've spent enough time in the guts of Core's build system to have a good idea of what to look for, not to mention Cory Fields, the Core build guru, gave a lot of good advice when he was lending a hand.)
Don't trust me? No problem! I encourage skeptics to roll their own versions. As long as everything's set up properly, you just run a set-it-and-forget-it script that should take ~20 min. to complete. Just be forewarned that the script is somewhat reliant on my particular system's setup. I shored it up a bit once I moved over to a VM. You may still have issues. Please let me know if you're having issues.
