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

cannot use self-built javacv #395

Closed
The-Crocop opened this issue Apr 25, 2016 · 5 comments
Closed

cannot use self-built javacv #395

The-Crocop opened this issue Apr 25, 2016 · 5 comments

Comments

@The-Crocop
Copy link

The-Crocop commented Apr 25, 2016

Hi Samuel I have builld all the javacv ,javacpp-presets and javacpp libraries myself. Im using Ubuntu and gradle.

I have those entries in my build.gradle:

repositories{
    mavenCentral()
    mavenLocal()
}
dependencies {
    compile 'org.bytedeco:javacv:1.2-SNAPSHOT'
    compile("org.bytedeco.javacpp-presets:opencv:3.1.0-1.2-SNAPSHOT:linux-x86_64")
    compile("org.bytedeco.javacpp-presets:ffmpeg:3.0.1-1.2-SNAPSHOT:linux-x86_64")
}

However the javacv dependency causes this error:

 Could not resolve all dependencies for configuration ':compile'.
 Could not find javacpp-presets-${os.name}-${os.arch}.jar (org.bytedeco:javacpp-presets:1.2-SNAPSHOT).
   Searched in the following locations:
     file:/home/user/.m2/repository/org/bytedeco/javacpp-presets/1.2-SNAPSHOT/javacpp-presets-1.2-SNAPSHOT-${os.name}-${os.arch}.jar

Any idea what might cause this?

I have build javacpp-presets with these commands:

bash cppbuild.sh -platform linux-x86_64 install
mvn clean install -Djavacpp.platform=linux-x86_64 -Djavacpp.platform.dependency=false

I have build javacv like this:

mvn clean install -Pffmpeg.
@saudet
Copy link
Member

saudet commented Apr 28, 2016

It looks like Gradle doesn't resolve the os.name and os.arch properties like Maven does. AFAIK, to get Gradle working perfectly, we would need to create a small special project for that. @lloydmeta has created sbt-javacv and sbt-javacpp to resolve these issues with sbt. Would you be interested in making the same thing for Gradle?

@The-Crocop
Copy link
Author

Sure. Id love to do that. Just give me some time.

@saudet
Copy link
Member

saudet commented Apr 29, 2016

Great! Keep me updated on your progress

@saudet
Copy link
Member

saudet commented May 19, 2016

I guess we shouldn't break things that used to work, even if it's caused by a bug in Gradle, so marking this as a bug. The workaround is to include this in the build.gradle file:

configurations {
    all*.exclude group: 'org.bytedeco', module: 'javacpp-presets'
}

talregev added a commit to talregev/android_cv_bridge that referenced this issue May 21, 2016
saudet added a commit that referenced this issue Jul 16, 2016
…ss-platform builds and to avoid issues with some build systems (issue #395)
saudet added a commit that referenced this issue Jul 22, 2016
…ss-platform builds and to avoid issues with some build systems (issue #395)
saudet added a commit that referenced this issue Jul 22, 2016
…ss-platform builds and to avoid issues with some build systems (issue #395)
saudet added a commit that referenced this issue Aug 15, 2016
…ss-platform builds and to avoid issues with some build systems (issue #395)
saudet added a commit that referenced this issue Oct 28, 2016
…ss-platform builds and to avoid issues with some build systems (issue #395)
@saudet
Copy link
Member

saudet commented Dec 9, 2016

The JavaCPP Presets and JavaCV 1.3 now rely on "platform artifacts", so we won't be having issues like this anymore with either Gradle or sbt! Thanks for reporting

@saudet saudet closed this as completed Dec 9, 2016
dljsjr pushed a commit to ihmcrobotics/ihmc_ros_core that referenced this issue Feb 22, 2017
See: bytedeco/javacv#395 for more information. This filtering was being done in our build scripts so .jars were built and emitted fine but the Java adapter was running in to this when trying to download all the .jars
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants