-
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
In a Windows environment, using JavaCV runs without issues; however, when running on Ubuntu 16.04, errors occur. #2199
Comments
Duplicate of bytedeco/javacpp-presets#1379 |
"Excuse me, would it be sufficient if I only set up OpenCV and FFmpeg compatible with JavaCV specifically for the production environment?" |
Yes, that works too, as long as the "org.bytedeco.javacpp.pathsFirst"
system property is set to "true".
|
I have added System.setProperty("org.bytedeco.javacpp.pathsFirst", "true"); in my launcher class, but I am still encountering the same error. |
In addition to setting System.setProperty("org.bytedeco.javacpp.pathsFirst", "true") in the launcher class, does merely installing FFmpeg and OpenCV on Ubuntu, along with configuring environment variables, suffice to specify the correct paths? |
Probably not. Please set the "org.bytedeco.javacpp.logger.debug" system property to "true" to get more information on the console. |
The JDK being used is version 8.
|
It's not trying to load libraries from your system, you need to call System.setProperty("org.bytedeco.javacpp.pathsFirst", "true") to do that |
I resolved the error by commenting on these two lines of code: (
Will this have any impact? |
Make sure that your libraries can actually be found in the system PATH |
No matter which version of JavaCV is packaged and running on the window, there is no problem. However, there are issues with both JavaCV 1.5.9 and JavaCV 1.5.10 on Ubuntu 16.04. How can I solve them?
pom(javacv1.5.9):
Error messages printed using Javacv1.5.9:
pom(javacv1.5.10):
Error messages printed using Javacv1.5.10:
The text was updated successfully, but these errors were encountered: