On Sun, Mar 16, 2025 at 12:02 PM, Bob Jacobsen wrote:
c) The bad news is that Rosetta 2 won’t be supported by Apple forever. Some future OS upgrade will remove it, at which point you won’t be able to use a native Anyma connection if you upgrade to that OS version.
Deprecation of Rosetta 2 is a complicated issue. The previous PowerPC-to-Intel incarnation of Rosetta was limited to about five years, so it's natural to assume that Apple will kill it with this fall's (2025) MacOS upgrade (or perhaps next year's). There are, however, two reasons that Rosetta 2 may hang around longer:
- Rosetta 2 was developed by Apple as opposed to Rosetta 1, which was licensed by Apple. That license arrangement encouraged Apple to kill support for it sooner rather than later.
- Rosetta 2 is also used in MacOS for x86-64 Linux virtual machines.?
Like you, I'm inclined to assume that it's going to go away, so I don't want to rely on it either.
d) The meh news is that we might eventually be able to fix this. We are distributing a .jar file that _should_ contain the necessary code, but for some reason it’s not working. That libusb4java file is maintained by a different software project and they might eventually provide a version that works on Apple Silicon.
The problem of the missing darwin-aarch64 code in the libusb4java project is pretty simple. While the script builds both darwin-x86-64 and darwin-aarch64, the script omits the darwin-aarch64 platform, so it's not in the jar file.?
Or somebody might take that open-source () and create one themselves.?
I don't love the idea from a maintainability standpoint, but forking our own libusb4java project could resolve this.
Sorry there doesn’t seem to be a more explicit answer.
Sometimes, that's the norm for distributed software development. I get it. We just have to rattle the necessary cages or roll our own until these dependent projects get some love.?
?
Best regards,
?
Paul
?
?
Paul Anderson