Hi Jan, > It uses pkg-config. > > $ pkg-config --exists libusb-1.0 && echo "libusb-1.0 exists!" > > >> /usr/local/lib/libusb-0.1.4.4.4.dylib /usr/local/lib/libusbdll.dylib >> > That's libusb0. > > >> /usr/local/lib/libusbpp-0.1.4.4.4.dylib >> /usr/local/lib/libusbpp-0.1.4.dylib /usr/local/lib/libusbpp.dylib >> /usr/local/lib/libusbpp.la >> > That's the C++ binding for libusb0, which owfs doesn't use.
I just replied to Johan and included pkg-config not finding libusb 1 while brew sees it. > Forget about the FUSE binding. It has some awkward limitations > introduced by the file system abstraction which makes it unusable for > anything but demonstration purposes. Ah… OK. Great. > Don't get the ./configure output wrong. owphp is the owlib based > language binding. You need this if you want to access the hardware > directly (without the help of owserver), which isn't recommended. Oh… I didn’t understand that. > It is recommended to use owserver and an ownet based client. The ownet > bindings have no external dependencies and are built by default. Look > into module/ownet/php/examples. OK. I’ll do that once I get owfs running. libusb seems to be the issues. Dean ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
