Hi Eduardo,
> > > 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.
> >
> > No. The libusb needs to be fixed, because it is their bug not to install
> > a libusb.pc file. The only other option is not to install the openobex
> > pkgconfig file at all.
>
> If not having pkg-config support is a bug on libusb, having a broken
> openobex.pc file seems to be a worse bug to me. But it is just my personal
> point of view.
The openobex.pc is not broken. That's a problem of pkg-config itself,
because in this case it misses something in the chain. The openobex.pc
file itself is fully correct. You miss a libusb.pc on your system. And
if this file is missing, it is a libusb bug.
> > > 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).
> >
> > Maybe from pkgconfig people, but people that detect openobex by themself
> > and others that use openobex.m4 it would be bad to not include libusb
> > support only because of a missing libusb.pc file.
>
> I think I got your point: currently a missing libusb.pc file will
> break openobex.pc but you think it is better than not supporting
> libusb-without-pkgconfig at all.
I will restrict people that use pkg-config for their library detection,
but again the openobex.pc file is correct. The missing libusb.pc is here
the problem.
> I was seeing the broken openobex.pc file as worse problem, and preferred
> just telling the user "get a newer libusb, otherwise your openobex
> install will be broken". I see it as a problem because I think
> pkg-config support is important for a library. It is just my personal
> view, anyway.
Again, openobex.pc is not broken. The libusb package misses a libusb.pc
file.
> Anway, I suggest the workaround below. It will affect only the pkg-config
> support on openobex (that is broken when using the upstream libusb,
> right now).
>
> Feel free to drop it if you still disagree with my point. I won't take
> it personally, I understood your point. :) But I just think that it
> is good to keep openobex pkgconfig working when using the upstream libusb.
This workaround makes it more worse. Now people can detect openobex
through pkg-config, but they never link with -lusb and this makes their
application also useless.
If it makes you happy, I can disable USB support at all if no libusb.pc
is found.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users
