On Thu, Jan 19, 2006 at 01:02:44PM +0100, Marcel Holtmann wrote: > Hi Eduardo,
Hi, > <snip> > > the openobex finds the libusb without libusb.pc and links against it. > Based on this it generates an openobex.pc which requires libusb.pc or > not. However the openobex library gets installed no matter what > libusb.pc exists or not. But it gets installed with a broken openobex.pc, as reported by Christian. > > You get into trouble if you use pkgconfig to detect openobex, but this > is not what you complained about. This was exactly what Christian had reported, and I said I had the same problem. But my message was confusing when I said that I needed a workaround to "build" openobex from CVS. > > > > > There is no .pc file on the upstream libusb tarball. The pkg-config > > > > support seems to be a feature added by the Ubuntu package. > > > > > > The libusb however contains a libusb.pc.in file. > > > > Not on this tarball: > > http://prdownloads.sourceforge.net/libusb/libusb-0.1.10a.tar.gz > > The CVS has it. So, openobex won't support the libusb version 0.1.10a as released from libusb.sf.net? If openobex will support only the libusb versions that containg a libusb.pc, why not using pkg-config to find libusb on configure? Otherwise, if libusb without libusb.pc is supposed to be supported, the generation of a broken openobex.pc in this case seems to need a fix. The current case seems a bit inconsistent to me: libusbwithout libusb.pc is supported at build time, but it generates an openobex install that isn't working completely ('pkg-config --cflags' openobex isn't working). -- Eduardo
pgpJ80pege8lD.pgp
Description: PGP signature
