-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Creation of Frame results in: No native JavaCPP library in memory. (Has Loader.load() been called?)
#1305
Comments
Now that JavaCPP produces a separate |
Hmm, just updated to 1.5.2 and I'm getting the same error. Did something change in the load order? The error trigger on this line:
And the error looks like this:
|
@razvanilin Nothing changed, it's always been like that. |
I was looking into this again and I found out that the issue is probably that in the previous version I was importing I think that causes the javaCPP library to not load. |
Is there a way to load the javaCPP library without doing I'm using an external
I had to exclude the opencv module in the javacv platform to avoid clash errors during the release build.
|
If you're using OpenCV, calling |
Still seeing this error. I am not using opencv but just using javacv version 1.5.2. |
@ulohani90 If you're not using OpenCV, call |
…x issues at load time (issue bytedeco/javacv#1305)
…artifact to fix issues at load time (issue bytedeco/javacv#1305)
This should now be fixed with the latest commits bytedeco/javacpp@abe3cf0 and bytedeco/javacpp-presets@d49542e. Please give it a try with the snapshots: http://bytedeco.org/builds/ @timothyjward This should also fix any last remaining roadblocks for OSGi. If you find anything else that we would need to do for OSGi though, please be sure to let me know! Assuming that everything is working now, the next step would be to update presets for OpenBLAS, OpenCV, etc, before moving on to Deeplearning4j, MXNet, TensorFlow, etc. |
The fix is now included in just released version 1.5.3. Thank you all for the feedback! |
Using some of the JavaCV classes may lead to exception:
Looks that JavaCV does not load JavaCPP libraries on its own. If something loads them first, there is no issue.
Simple code to reproduce the exception:
If you uncomment the line with
CV_VERSION
there is no exception, as OpenCV wrapper will load JavaCPP libraries.The text was updated successfully, but these errors were encountered: