My fault, I neglected to re-read the developers guide. I had just taken the openups-usb.* and copied them, and then copied all their entries in various makefiles and changed them to match my files instead. That wasn't enough, apparently.
I'll try following the guide verbatim instead and see how well that works for me. Sincerely, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:[email protected]] > Sent: Monday, March 02, 2015 8:27 PM > To: Rob Groner > Cc: nut-upsuser List > Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut > 2.7.2 > > On Mar 2, 2015, at 12:49 PM, Rob Groner <[email protected]> wrote: > > > Well, having spent a decent amount of time trying to get my driver file > added into the Makefile build system (and failing), I've decided that for now, > simply adding that one line to the openups-hid.c file and recompiling is the > best route to go. When I can no longer live with the limited nature of the > openups-hid driver, I'll revisit writing our own. > > I'll take this as a TODO item to make it clearer, but for later the basic > information is here: > > http://www.networkupstools.org/docs/developer- > guide.chunked/ar01s04.html#_writing_a_subdriver > > "You must also add the subdriver to USBHID_UPS_SUBDRIVERS in > drivers/Makefile.am and call "autoreconf" and/or "./configure" from the top > level NUT directory." > > To run autoreconf, you need automake, autoconf and libtool. automake > turns Makefile.am into Makefile.in, and the ./configure script converts > Makefile.in to the Makefile. > > -- > Charles Lepple > clepple@gmail > > _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
