-
Notifications
You must be signed in to change notification settings - Fork 582
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
Warning: Could not load X: java.lang.UnsatisfiedLinkError: no jnijavacpp in java.library.path #393
Comments
As explained at bytedeco/javacv#1305 we now need to add a dependency on an artifact containing that library, that is all. All presets have already been updated, so we don't need to do anything special. How are you getting this warning? |
Based on bytedeco/javacv#1305 discussion, It is not clear to me what dependency should be added. I updated the flandmark example to use JavaCPP 1.5.3. It illustrates the issue.
Here is the code from SBT configuration (build.sbt) that sets the dependencies: // Platform classifier for native library dependencies
lazy val platform = org.bytedeco.javacpp.Loader.getPlatform
// @formatter:off
libraryDependencies ++= Seq(
"org.bytedeco" % "javacv" % "1.5.3",
"org.bytedeco" % "flandmark" % "1.07-1.5.3" classifier "",
"org.bytedeco" % "flandmark" % "1.07-1.5.3" classifier platform,
"org.bytedeco" % "openblas" % "0.3.9-1.5.3" classifier "",
"org.bytedeco" % "openblas" % "0.3.9-1.5.3" classifier platform,
"org.bytedeco" % "opencv" % "4.3.0-1.5.3" classifier "",
"org.bytedeco" % "opencv" % "4.3.0-1.5.3" classifier platform
) Do you mean that some additional dependency should be added here? |
You're missing this dependency:
|
That solves part of the problem. Adding the dependency stops warnings after SBT loaded and executes code. The remaining problem is that On other hand, |
Right, we don't need the native code for Loader.getPlatform()...
|
Unless you're OK with unfixing bytedeco/javacv#1305, yes we need that warning/error. |
If sbt uses a different class loader for executing |
Looks that logging levels are right now hard coded, so it will be good to have flexibility to set them through API. In case of When |
We can't transparently disable the warning without risking to unfix bytedeco/javacv#1305. You're the one who posted it, so I'm sure you wouldn't like that! But I think we can work around the problem by moving the code for |
Ok, I've added the |
Thanks. It works well with the new |
I am getting warnings while running JavaCPP 1.5.3 or JavaCPP presets (VideoInput etc) on Windows
where [...] is the system path variable value
The code seems to be working, just the warnings being printed.
Some hints what may be going on?
The text was updated successfully, but these errors were encountered: