Open GoogleCodeExporter opened 8 years ago
This sounds like you haven't installed the drivers properly for the Mac. Did
you follow this tutorial here:
http://c4c.posterous.com/installing-openni-kinect-drivers-and-nite-on.
Original comment by mosaic...@gmail.com
on 4 May 2011 at 5:52
I had this problem earlier... all you have to do is open up terminal type 'cd'
and type in the directory name with all the files then type './' and the the
file you want to run.
hope this helped
Original comment by williamf...@gmail.com
on 10 May 2011 at 11:07
I am also encountering this problems when running from the command line. I have
reinstalled the openni drivers and have (of course) run the application from
the shell with the ./ execution prefix. What concerns me is the reference to
local folders in the stack trace ("../../Bin/Release/libXnVNite.dylib" appears
to be trying to search for the Nite.dylib file relative to the application as
opposed to an absolute system location like opt or usr). I get this same result
with all versions of the app.
Thanks n keep up the cool work,
Brady Georgen
Original comment by pbradyge...@gmail.com
on 26 Jun 2011 at 11:46
Let me please chime in with a concern as per pbradyge...@gmail.com - as it
appears that there is some embedded reference to the mysterious
"../../Bin/Release" folder in the pre-compiled libs used.
Would somebody associated with the build of these libs please attend to this -
there's no other reference to this folder in any of the sample code. THANKS!
It would be great if the installer script(s) deposited these libs in a good
location such as "/usr/lib/openni"
BTW - I am developing in MacOSX 10.6+
One final note - OpenNI ROCKS!
Original comment by hydrates...@gmail.com
on 13 Jul 2011 at 6:49
Another thing you can do - which I did and it worked for me - was to use a
binary editor, such as RESORCERER - from Mathemaesthetics where I executed a
FIND AND REPLACE of "../../Bin/Release" with "/usr/lib/openni__" - there were
several instances of this string in both the libOpenNI.dylib and
libXnVNite.dylib files.
If you do not have RESORCERER - I believe there are other binary-file edit
tools - but can't suggest any off the top of my head.
To support this change, I created the folder at the path via the command: sudo
mkdir /usr/lib/openni__
Then I copied the modified files into the folder and added the LIBRARY SEARCH
PATH reference into my Xcode project as "usr/lib/openni__" - see attached
image.
One other consideration - to actually ADD the two lib files to your project, it
does not seem like there's a good way to point the MacOS Finder's file
navigator to the path of /usr/lib/openni__ - so, for the purposes of BUILDING,
I have simply added the files from a convenient location - then, when the
application execution takes place, the runtime code is looking for the two libs
at the /usr/lib/openni__ path - and all is well.
Original comment by hydrates...@gmail.com
on 13 Jul 2011 at 7:32
Attachments:
Original issue reported on code.google.com by
vrl...@gmail.com
on 2 May 2011 at 3:55