On 08/11/2013 12:55 PM, John Fehr wrote:
> It took me a while but eventually I figured out that it was using a
> Properties file from a download somehow, so I removed me ~/.m2 folder,
> and ran 'mvn install' in the javacpp folder, which ran without errors,
> and then ran 'mvn install' again in the javacv folder. This time it
> worked without errors.
Yes, JavaCPP and JavaCV need to be in sync. I make changes that break
compatibility with previous versions sometimes, but the repositories
should be in sync. I'm not sure how to make this work nicely with Maven
version numbers, but I think anyway I'll be moving at some point the
native stuff in JavaCV to some new subproject of JavaCPP.
> I could also now right click on the JavaCV project in Netbeans and
> build. (Some java files still have red !'s on them, so I'm not sure
> what's going on there, but it built without errors. The errors all seem
> to be with finding the com.jogamp.opencl.* stuff, but I can't find where
> I can specify the location of that.)
Yes, you can ignore those if you don't plan on using JogAmp. We need to
install JogAmp in the CLASSPATH somehow, because they don't provide
Maven artifacts.
Samuel