rgbdemo / nestk

C++ Library for Kinect
http://nicolas.burrus.name/index.php/Research/KinectUseNestk
Other
78 stars 45 forks source link

fixes to OS X compilation and support for OpenCV 2.2 compilation in libfreenect #1

Closed chazmatazz closed 13 years ago

chazmatazz commented 13 years ago

fixes to OS X compilation and support for OpenCV 2.2 compilation in libfreenect. I don't know what those lines in ntk/CMakeList.txt are supposed to do, but apparently I don't need them...

nburrus commented 13 years ago

Hi,

1) Are you using FIND_PACKAGE(OpenCV) to integrate OpenCV in your app ? If this is the case, the name of the libraries should be automatically defined.

2) The APPLE specific lines are set to avoid dynamic libraries loading issues when the binary expect them to be in some directory. This happens with OpenNI/Nite backend. It might have failed in your setup if you did not define the LIBRARY_OUTPUT_PATH cmake variable in the top project that includes nestk. This should be optional though, and an additional test would probably be welcome.

Thanks for pointing out these issues,

chazmatazz commented 13 years ago

Hi Nicolas,

Thanks for replying.

1) Yes, that works. Thanks.

2) Yes, but some dylibs are created after nestk is built, so they don't get copied. I moved those lines up to my top level CMakeLists.txt. See https://github.com/chazmatazz/Geonect (very early stages, no real coding done yet but the build works).

Best, Charles

On Thu, Apr 7, 2011 at 7:12 AM, nburrus < reply@reply.github.com>wrote:

Hi,

1) Are you using FIND_PACKAGE(OpenCV) to integrate OpenCV in your app ? If this is the case, the name of the libraries should be automatically defined.

2) The APPLE specific lines are set to avoid dynamic libraries loading issues when the binary expect them to be in some directory. This happens with OpenNI/Nite backend. It might have failed in your setup if you did not define the LIBRARY_OUTPUT_PATH cmake variable in the top project that includes nestk. This should be optional though, and an additional test would probably be welcome.

Thanks for pointing out these issues,

Reply to this email directly or view it on GitHub: https://github.com/nburrus/nestk/pull/1#issuecomment-968735

Charles