search for: libusb_lib

Displaying 8 results from an estimated 8 matches for "libusb_lib".

Did you mean: libusb_libs
2014 Oct 20
1
[PATCH] missing -lm in drivers/Makefile
...Regards, diff -Naubr nut-2.7.2.old/drivers/Makefile.am nut-2.7.2.new/drivers/Makefile.am --- nut-2.7.2.old/drivers/Makefile.am 2014-02-27 22:17:32.000000000 +0100 +++ nut-2.7.2.new/drivers/Makefile.am 2014-10-20 15:50:31.000000000 +0200 @@ -171,7 +171,7 @@ tripplite_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) -lm bcmxcp_usb_SOURCES = bcmxcp_usb.c bcmxcp.c usb-common.c -bcmxcp_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) +bcmxcp_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) -lm blazer_usb_SOURCES = blazer.c blazer_usb.c libusb.c usb-common.c blazer_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) -lm di...
2005 Sep 12
1
Re: Status of the PSE NUT patches (was: NUT patches)
[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >
2005 Nov 08
1
adding libusb CFLAGS to generic-hid.c rule
Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with
2024 Nov 02
1
Driver with calls to USB functions not linking
Do your drivers/Makefile.am rules for the resulting new program specify dependencies to use similar to other USB-capable drivers? e.g. ```` blazer_usb_SOURCES = blazer.c blazer_usb.c $(LIBUSB_IMPL) usb-common.c blazer_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) -lm ```` Jim On Sat, Nov 2, 2024 at 2:30?AM William R. Elliot <bill at wreassoc.com> wrote: > Hello again all. > > I am trying to use USB functions (non-HID) and I get a linker error > for functions that are in the included usb-common.h file. > > Specifically, at the st...
2024 Nov 02
1
Driver with calls to USB functions not linking
Hello again all. I am trying to use USB functions (non-HID) and I get a linker error for functions that are in the included usb-common.h file. Specifically, at the start, these functions: - warn_if_bad_usb_port_filename - nutusb_open - is_usb_device_supported Clearly the headers are there or I don't think the driver would compile. Can someone point me in the right direction please? Thank
2006 Mar 06
3
newhidups / Solaris 10 / APC RM1500
Hi there, been using NUT for ages and recently upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read
2006 Dec 05
3
megatec over USB - new driver patch
...terguard.c -megatec_SOURCES = megatec.c +megatec_SOURCES = megatec.c megatec_ser.c metasys_SOURCES = metasys.c mge_shut_SOURCES = mge-shut.c hidparser.c mge_utalk_SOURCES = mge-utalk.c @@ -133,6 +133,10 @@ bcmxcp_usb_CFLAGS = $(AM_CFLAGS) $(LIBUSB_CFLAGS) bcmxcp_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) +megatec_usb_SOURCES = megatec.c megatec_usb.c libusb.c +megatec_usb_CFLAGS = $(AM_CFLAGS) $(LIBUSB_CFLAGS) +megatec_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) + # USB-over-serial newmge_shut_SOURCES = newhidups.c libshut.c libhid.c hidparser.c mge-hid.c newmge_shut_CFLAGS = $(AM_CFLAGS) -D...
2007 Jan 23
2
Voltage override in megatec and megatec-over-usb [was: Re: nut-2.0.5 megatec + Online Xanto]
On 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out