added troubleshooting section to README.md

[chazmatazz]

Hi, I added a troubleshooting section to the README. We spent several hours trying to understand these issues (partially due to inexperience with java/clojure dependencies).

[aperiodic]

If you have to manually add the SimpleOpenNI.jnilib file to the classpath as in the second bullet point, that's a bug! When I run lein deps in the project root, all the native dependencies are extracted from simple-open-ni-0.xx.0.jar and placed in the corresponding folders under native. Is this not the case for you? If so, what version of leiningen are you using?

[chazmatazz]

Interesting! I am using Leiningen 2 on OS X and Linux Mint.

On Sat, Jun 9, 2012 at 12:04 PM, Dan Lidral-Porter <
reply@reply.github.com

wrote:

If you have to manually add the SimpleOpenNI.jnilib file to the classpath
as in the second bullet point, that's a bug! When I run lein deps in the
project root, all the native dependencies are extracted from
simple-open-ni-0.xx.0.jar and placed in the corresponding folders under
native. Is this not the case for you? If so, what version of leiningen are
you using?

---

Reply to this email directly or view it on GitHub:
#3 (comment)

Charles

[chazmatazz]

That's both OS X and Linux Mint (2 different computers). Yes, I think it is a Leiningen issue.

[chazmatazz]

I updated README.md to reflect that it is probably a Leiningen 2 issue.

Also, the scene image wasn't ever enabled, so it couldn't be used. I hacked in the enable, though probably this should be more-fine grained enabling (e.g. only when depth image or scene image requested). I also added rgb image. Rgb video feed is tearing on my install, not sure where this bug is.

I am done with the project this was used for (openni-overtone) and am probably switching to a Windows Kinect + the official SDK. Thanks, this project helped.