On Thu, Jul 30, 2020 at 6:26 PM Ryan Schmidt <libf...@ryandesign.com> wrote: > > On Jul 30, 2020, at 05:13, b...@elektron.ikp.physik.tu-darmstadt.de wrote: > > > > to my knowledge the accepted path to libusb.h for libusb1 is > > /usr/lib(xx)/libusb-1.0/libusb.h > ... > > Does libftdi also work with libusb0? If not, I think it should be > > #include <libusb-1.0/libusb.h> > > I don't know about cmake, but that at least doesn't appear to be > how pkg-config intends libusb to be used: > > $ pkg-config --cflags libusb-1.0 > -I/opt/local/include/libusb-1.0 > > So, -I/opt/local/include/libusb-1.0 is expected to be in CFLAGS, which means > that when you #include a libusb-1.0 file, you would list the path to the file > relative to /opt/local/include/libusb-1.0, in other words #include <libusb.h> > is correct.
Yes, exactly. pkg-config is the right way to go. -- Xiaofan (one of the admins of libusb project, on the support and testing side) -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to libftdi+unsubscr...@developer.intra2net.com
