Closed GoogleCodeExporter closed 8 years ago
No, you didn't.
Original comment by samuel.a...@gmail.com
on 15 Jun 2012 at 11:41
ok . you are right... but I definitely didn't build it myself.
There are issues...
1. I had to download jogamp manually and install it into the local maven repo
(see attached script). shld be already in repo.
2. I created a jar file containing opencv native libs. but there is no way to
extract and let opencv_core and other know where these libraries are.
I tried stopped the debugger and put my libs into the temp folder created for jni libs and the demo worked(tested only on mac).
3. Excluded PS3EyeFrameGrabber. Not sure how to compile it. Does any1 really
use it?
Original comment by Jkolo...@gmail.com
on 19 Jun 2012 at 3:04
Attachments:
1. Have you tried contacting the authors of JogAmp see what they think of your
script?
2. If you put the JAR file in the classpath, it looks to me like it should work
automatically.
3. There's other stuff too...
Original comment by samuel.a...@gmail.com
on 20 Jun 2012 at 2:50
1. No I haven't. They don't care about maven.. at least right now. As I said
before we just need a copy of jogam into javacv maven repo once and make it
optional and forget about it(until the next version).
2. unfortunately it doesn't work this way. it exracts jni libs one by one and
after extracting it tries to load dependent libraries from java.library.path .
for example it extract libjniopencv_core.dylib and then starts to look for
libopencv_core.dylib in the same temporary directory where
libjniopencv_core.dylib was extracted.
Original comment by Jkolo...@gmail.com
on 20 Jun 2012 at 9:33
[deleted comment]
Well, it works just fine with the FaceApplet, so it should work. If you can
figure out what is wrong, please let me know, especially if it's a bug, thank
you.
Original comment by samuel.a...@gmail.com
on 21 Jun 2012 at 1:16
I've just released JavaCV 0.2, and it now comes with a pom.xml file that does
not depend by default on anything else than OpenCV and a C++ compiler for
JavaCPP. So, I guess this fixes this issue. Let me know if you still have
issues building JavaCV from source.
As for packaging binaries of OpenCV and FFmpeg, well, until I figure out a way
to automate all their builds properly, I welcome any contribution! Please open
another issue concerning that, and keep me updated on your progress there,
thank you.
Original comment by samuel.a...@gmail.com
on 22 Jul 2012 at 5:42
Hi, I'm trying to install JavaCV 0.2 using maven right now and I can't seem to
get the jar javacv-0.2-linux-x86_64.jar to be included. I did mvn clean install
in javacv and got the following packages installed into local maven repo:
- javacv-0.2.jar
- javacpp-0.2.jar
- *javacv-0.2-linux-x86_64.jar
* - however this last jar would not get included in the imported maven projects.
My pom.xml that calls javacv is:
<dependency>
<groupId>com.googlecode.javacv</groupId>
<artifactId>javacv</artifactId>
<version>0.2</version>
</dependency>
How can I get it to recognize that it's a linux x86_64 machine in this
definition? Also, you mentioned that openCV needs to be installed in the
default location for the mvn install to work properly. Where is that exactly? I
have it installed in the same folder as javaCV.
Thanks!
Original comment by raymend...@gmail.com
on 14 Aug 2012 at 5:00
@raymend.li Check the pom.xml file of ProCamCalib or ProCamTracker for an
example of what you ask:
http://procamcalib.javacv.googlecode.com/git/pom.xml
http://procamtracker.javacv.googlecode.com/git/pom.xml
As for OpenCV, that depends on your platform, but in Linux it would usually get
installed in /usr/local/lib/
Original comment by samuel.a...@gmail.com
on 15 Aug 2012 at 11:30
Original issue reported on code.google.com by
kuznetsov.alexey
on 13 May 2012 at 10:05