- [x] Require arm64 OpenJDK (i.e. JEP 391: macOS/AArch64 Port)
- [_] Require x86_64 + arm64 universal binary OpenJDK (required for Mac App Store submission)
- [x] Require arm64 libjnidispatch.dylib binaries
- [x] Require arm64 libjcocoa.dylib binaries
- [x] Require arm64 libmediainfo.dylib binaries
- [_] Require arm64 lib7-Zip-JBinding.dylib binaries (optional; can use 7z binaries as an alternative)
- [x] Require arm64 fpcalc binaries
- [x] Require arm64 appbundler support
UPDATE: 10 Feb 2024
Universal JDK (as opposed to architecture-specific JDK) is not viable. The App Store Connect developer interface does not support the upload of multiple app bundles per architecture neither, so we are at an impasse. We can use lipo to combine binaries and libraries, but architecture-specific runtime resource files (notably jrt-fs.jar, modules, classlist, etc) are an unsolved (i.e. unsolvable to us; but easily solvable by Apple if someone were to care) problem. The lipo tool cannot combine resource files and the JDK wouldn't be able to work with combined resource files even if we could combine them. Notably, the Mac App Store does not currently allow submissions where an arm64-only version replaces a previously released x64-only version.