#27979: libdc1394 requires libusb, conflicts with libusb-devel, which is more stable. -------------------------------+-------------------------------------------- Reporter: njbutko@… | Owner: mail@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: libdc1394 -------------------------------+-------------------------------------------- Comment(by njbutko@…): Replying to [comment:5 jmr@…]:
OK, so "problems with the kinect" is a little less vague. But can you point out the specific problems?
Unfortunately, I don't really know the specifics of the problems. I only have a vague idea based on talking to the developers of libfreenect a few months ago. Their opinion was that libusb was buggy in many of its more advanced features. Specifically, they were finding that Apple's IOKit had a lot of poorly documented specifications that were difficult to follow correctly, and that libusb didn't follow them correctly. So, they patched up the parts of libusb that needed patching to get the Kinect to work. They submitted the patches, and then were frustrated by libusb's slow release schedule. They got the patches pushed into the development branch, and the development branch is currently required for anyone working with a kinect. There is a lot of overlap with people using kinect and libdc1394 (basically anyone doing computer vision), and it would be nice for them to be compatible. I'm not sure what a good general policy for this sort of thing is. On the one hand, development versions are inherently unstable, because new features are being added. However, it sucks when the "stable" version has bugs that make it unusable. -- Ticket URL: <https://trac.macports.org/ticket/27979#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS