Package Details: libfreenect2 0.2.1-4

Git Clone URL: https://aur.archlinux.org/libfreenect2.git (read-only, click to copy)
Package Base: libfreenect2
Description: Open source drivers for the Kinect for Windows v2
Upstream URL: http://openkinect.org
Licenses: GPL, Apache
Submitter: de-vries
Maintainer: grandchild
Last Packager: grandchild
Votes: 9
Popularity: 0.000000
First Submitted: 2015-12-02 17:26 (UTC)
Last Updated: 2023-11-16 16:01 (UTC)

Latest Comments

« First ‹ Previous 1 2 3

fepf commented on 2015-12-22 13:10 (UTC)

When i install with makepkg, oddly the ldd for Protonect points to the libfreenect2.so that is still in the makepkg build folder. It does not seem to get installed into /usr/lib. So i did not use a chroot environment. In /usr/lib the pacaur-version of libfreenect2.so seems to be still present. The pacaur-version of the executable correctly point to this lib. sha256sum of the Protonect versions were the same, but differed for the library. An object-dump-diff of the library-versions reveals the missing symbols and the differing RPATH: /usr/lib (makepkg) vs /usr/local/lib (pacaur). Could be a hint for a difference in the compiling process. Maybe some of the depenencies were not found (using a wrong RPATH) and therefore some functions were disabled. But only while compiling the lib and not during the compiling of the executable. Also the ldd of the make-pkg version of Protonect is about 30 lines, whereas of the not-working-pacaur-version its about 151 lines. Btw. yaourt gives the same error. But anyway. Dont put too much effort in it, since the libfreenect2 project will certainly change. Anyone having trouble installing this package with pacaur/yourt should try the manual method.

de-vries commented on 2015-12-22 10:39 (UTC)

I don't have a kinect 2 at home, so I can only see if the executable will run, not if it really works (I can test at work soon). But I didn't get symbol lookup errors when running protonect when installed manually with makepkg, with pacaur or when built in a clean chroot. Does pacaur build in a chroot? If not I can't see why building with pacaur vs makepkg should make a difference. Can you check the ouput of `ldd /usr/bin/Protonect`?

fepf commented on 2015-12-22 10:06 (UTC)

I'm using pacaur to install AUR packages, and thats usually working fine. Except for this package (tried on two hosts). Installing seems flawless, but when trying to start the Protonect executable, a symbol lookup error occurs (some symbol to a console logger function, probably defined in the freenect lib). Oddly using the old-fashioned way (downloading PKGBUILD, makepkg and pacman -U) it works. Althought installing by pacaur and installing manually should essentially do the same. It may be the fault of pacaur (or my entire setups) and not this package, but this is the first one on witch i experienced such behaviour. Can someone (de-vries maybe :-) ) verify this error ?

« First ‹ Previous 1 2 3