Skip to content
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

Issue to built the lib for Raspberry PI (arm and x86) #105

Open
f41ardu opened this issue Dec 29, 2017 · 2 comments
Open

Issue to built the lib for Raspberry PI (arm and x86) #105

f41ardu opened this issue Dec 29, 2017 · 2 comments

Comments

@f41ardu
Copy link

f41ardu commented Dec 29, 2017

It is realy weired.

Using ldd show that the dynamic libraries are not resolved.
As soon as I copy a library (i,e, /libopencv_java245.so) into my /tmp
ldd shows the correct linked libs?

Strange, isn't it. No idea where does that come from.

While bullding the opencv-processing library I run in some minor issues.
Building the library on Windows 8.1 it works fine on Window 8.1up to the latest Processing release.
Moving the library to Raspberry PI (x86 and ARM) I get follwing error:

UnsatisfiedLinkError:
/home/pi/sketchbook/libraries/opencv_processing/library/linux32/libopencv_java245.so:
/home/pi/sketchbook/libraries/opencv_processing/library/linux32/libopencv_core.so.2.4:
file too short
A library relies on native code that's not available.
Or only works properly when the sketch is run as a 64-bit application.

But both files are there.

This appreas either on Raspberry x86 and arm.
While using the library downloaded from github it is working for platforms.

I built it on all platforms with the same result. Works fine on Windows but not on Raspberry.

@f41ardu
Copy link
Author

f41ardu commented Dec 29, 2017

Looks like an issue with the shared libs distributed while getting the package as ZIP file.
I recoverd all shared libs from the path where my Processing Libs are located int the Eclipse workspace and
my own built lib is working now.

@f41ardu f41ardu closed this as completed Dec 29, 2017
@f41ardu f41ardu reopened this Dec 29, 2017
@f41ardu
Copy link
Author

f41ardu commented Dec 29, 2017

That mean I have a workaround now. But the issue isn't fixed yet.
Any plans to move to a later release of opencv like 3.0 or higher?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant