search for: nut_have_libusb

...onditionally. > > if --with-usb is not passed. Not sure why; the HIDDEV macro is defined > conditionally, and I definitely don't have hiddev on OS X. I will revisit this > when I am more awake. This just means that the following two lines: AM_CONDITIONAL(HAVE_LIBUSB, test "${nut_have_libusb}" = "yes") AM_CONDITIONAL(HAVE_HIDDEV, test -n "${linux_hiddev}") are not allowed to appear inside "if ... fi". This makes sense, as automake-conditionals have to be defined regardless. You have to move these lines to after the section you "conditioned out&q...

On Sep 18, 2015, at 2:45 PM, Rob Groner <rgroner at RTD.com> wrote: > > Well, I've spent a couple hours on this, unable to figure it out. I removed the libusb-compat-devel package using zypper. And I've downloaded, built, and installed libusb from sourceforge. But trying to configure nut now I get "USB drivers requested, but libusb not found", no matter what I put

...in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. > > It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". You have: ./configure --with-usb --with-dev --with-usb-includes=/usr/local/include --with-usb-libs=-L=/usr/local/lib64 I think you want: ./configure --with-usb --with-dev --with-usb-i...

...t, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. >> >> It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". > > You have: > > ./configure --with-usb --with-dev --with-usb-includes=/usr/local/include --with-usb-libs=-L=/usr/local/lib64 > > I think you want: > > ./configur...

...ow looking in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". Rob Groner Software Engineer Level II RTD Embedded Technologies, Inc. ISO 9001 and AS9100 Certified Ph: +1 814-234-8087 www.rtd.com -----Original Message----- From: Charles Lepple [ma...

...in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. > > It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". You have: ./configure --with-usb --with-dev --with-usb-includes=/usr/local/include --with-usb-libs=-L=/usr/local/lib64 I think you want: ./configure --with-usb --with-dev --with-usb-i...

Peter, similar to the OpenSSL test and "with_ssl", can we make the libusb test in configure.in depend on "with_usb=yes"? It's not as important as not linking against OpenSSL unless requested, but it caused a bit of confusion when I was trying to rebuild. I forgot that "--with-drivers=all" does not imply "--with-usb", and it was not registering that the

...'t see anything more than I already thought I knew. It's as cryptic as configure itself. >>> >>> It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". >> >> You have: >> >> ./configure --with-usb --with-dev >> --with-usb-includes=/usr/local/include >> --with-usb-libs=-L=/usr/local/lib64 >> >&...

...t, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. >> >> It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". > > You have: > > ./configure --with-usb --with-dev > --with-usb-includes=/usr/local/include > --with-usb-libs=-L=/usr/local/lib64 > > I think you want: > &gt...

...'t see anything more than I already thought I knew. It's as cryptic as configure itself. >>> >>> It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what they're looking for. Clearly somehow, that is supposed to be set to "yes". >> >> You have: >> >> ./configure --with-usb --with-dev >> --with-usb-includes=/usr/local/include >> --with-usb-libs=-L=/usr/local/lib64 >> >&...