New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maven project call webcam-capture fail on aarch64 platform #878
Comments
|
offical OpenImaj does not include aarch64, i.e. arm64. |
I got it, thank you! I already changed to use opencv |
is it possible to add what is necessary to make OpenImaj work on aarch64 ? recently bridj includes the files for aarch64 in its latest version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
maven project call webcam-capture fail on aarch64 platform
get exceptions:
java.lang.RuntimeException: Failed to initialize BridJ (java.lang.UnsatisfiedLinkError: /tmp/BridJExtractedLibraries2069336107326078457/libbridj.so: /tmp/BridJExtractedLibraries2069336107326078457/libbridj.so: 无法打开共享对象文件: 没有那个文件或目录 (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform))
at org.bridj.Platform.initLibrary(Platform.java:444)
at org.bridj.Platform.(Platform.java:228)
at com.github.sarxos.webcam.ds.buildin.natives.OpenIMAJGrabber.(OpenIMAJGrabber.java:59)
at com.github.sarxos.webcam.ds.buildin.WebcamDefaultDriver$WebcamNewGrabberTask.handle(WebcamDefaultDriver.java:55)
at com.github.sarxos.webcam.WebcamProcessor$AtomicProcessor.run(WebcamProcessor.java:81)
Caused by: java.lang.UnsatisfiedLinkError: org.bridj.Platform.sizeOf_ptrdiff_t()I
at org.bridj.Platform.sizeOf_ptrdiff_t(Native Method)
at org.bridj.Platform.(Platform.java:232)
at com.github.sarxos.webcam.ds.buildin.natives.OpenIMAJGrabber.(OpenIMAJGrabber.java:59)
at com.github.sarxos.webcam.ds.buildin.WebcamDefaultDriver$WebcamNewGrabberTask.handle(WebcamDefaultDriver.java:55)
at com.github.sarxos.webcam.WebcamProcessor$AtomicProcessor.run(WebcamProcessor.java:81)
my maven config:
`
com.github.sarxos
webcam-capture
0.3.12
The text was updated successfully, but these errors were encountered: