my universal imagej-macosx (x86/arm64), with no JRE:.Wrong architecture error, system Java fallback, launches Fiji, No issues. my universal imagej-macosx (x86/arm64), with current official JRE (x86):.
current official imagej-macosx (x86), with native JRE inside Fiji.app (Azul 11 in my case):. Launches Fiji after fallback to System Java. current official imagej-macosx (x86), with no JRE and native system Java (Azul 11 in my case):. current official imagej-macosx (x86), with current official JRE (x86):. It works fine with the following behavior when launched from the command line to monitor errors (there's some warnings too regarding patcher/injector, but they seem of no issue): I've tested this binary on my Apple Silicon M1 Mac. ~/dev/imagej-launcher > lipo -info ImageJ-macosxĪrchitectures in the fat file: ImageJ-macosx are: x86_64 arm64` The project compiled with no issue and the binary is universal: I also had some Java path issues, which may be a Big Sur thing. I made a fork ( ) and tweaked CMakeLists.txt to provide the two arch for cmake (to make a universal binary). 
This is also supported by cmake, which I was pleased to see is used by the imagej-launcher. It does report an architecture mismatch error and does a fallback to system Java, which results in a 2nd Fiji icon in the dock-minor inconvenience.Īs noted in the thread, Apple docs show you can build for a different architecture than you run (can't test obviously) and can build universal binaries. Non-fat file: ImageJ-macosx is architecture: x86_64 Applications/Fiji.app/Contents/MacOS> lipo -info ImageJ-macosx
0 kommentar(er)
