question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

plugin downloads wrong architecture for macOS M1

See original GitHub issue

I’m running on macOS with a Silicon (M1) chip.

I set the version in the plugin to 17, which should download openjfx 17, which has M1 support.

When I run my application, I get the following error:

Loading library prism_es2 from resource failed: java.lang.UnsatisfiedLinkError: /Users/vewert/.openjfx/cache/17/libprism_es2.dylib: dlopen(/Users/vewert/.openjfx/cache/17/libprism_es2.dylib, 1): no suitable image found.  Did find:
	/Users/vewert/.openjfx/cache/17/libprism_es2.dylib: mach-o, but wrong architecture
	/Users/vewert/.openjfx/cache/17/libprism_es2.dylib: stat() failed with errno=38

I checked /Users/vewert/.openjfx/cache/17/ and ran file libprism_es2.dylib and got: libprism_es2.dylib: Mach-O 64-bit dynamically linked shared library x86_64 which makes it look like it has downloaded the Intel libraries instead of the M1 libraries.

I’m not sure if the problem is that the M1 version isn’t available on Maven Central, or the plugin is downloading the wrong one.

As a work around, I downloaded the JavaFX 17 jdk, set a local sdk: https://github.com/openjfx/javafx-gradle-plugin#5-using-a-local-javafx-sdk

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:8
  • Comments:7

github_iconTop GitHub Comments

5reactions
hohonuulicommented, Nov 15, 2021

@henryhchchc Thanks for addressing this

Anyone have a timeline when this a new release with this fix will be published?

2reactions
cryptoAlgorithmcommented, Apr 10, 2022

In build.gradle change the javafx plugin version to 0.0.11 or above, for example:

plugins {
    id 'java'
    id 'application'
    id 'org.openjfx.javafxplugin' version '0.0.11'
}
Read more comments on GitHub >

github_iconTop Results From Across the Web

Can't build to simulator on Apple … | Apple Developer Forums
It only popped up when trying to build on my new M1 MacBook Air and Xcode 12. I've tried everything that's been reported...
Read more >
Issue with synth plugin and Apple M1 Max chip - Statalist
I'm guessing this is because the macOS version was originally compiled for a 32 bit architecture, which is no longer supported by your...
Read more >
M1 mac: mach-o file, but is an incompatible architecture (have ...
The error you have is that lxml has been built as an Intel binary. Looking at the downloads for lxml at pypi there...
Read more >
Develop on Apple Silicon (M1) macOS
However, Apple M1 does not work with protobuf 2.5.0 - when installing protobuf from source you will get unsupported CPU architecture error.
Read more >
Apple Silicon M1 Compatibility Chart for Spitfire Audio Libraries
Please use the tables below to check the compatibility of your DAW and Spitfire Audio Plugins. If the plugin you wish to use...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found