search for: ci_build

...binaries do appear and some do run without crashing on Windows - e.g. usbhid-ups and nut-scanner did see my test UPS. Fixes originally made for libusb-0.1 were applied to libusb1.c too, but not tried yet. Builds are possible, mostly scripted and documented, see: * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) natively on Windows, * `scripts/Windows/README` and a build script nearby for using mingw cross-building packages on Ubuntu Linux. Both of these produce lots of standalone usable binaries installable as a typical NUT directory tree, which (with copies of DLLs for thi...

...binaries do appear and some do run without crashing on Windows - e.g. usbhid-ups and nut-scanner did see my test UPS. Fixes originally made for libusb-0.1 were applied to libusb1.c too, but not tried yet. Builds are possible, mostly scripted and documented, see: * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) natively on Windows, * `scripts/Windows/README` and a build script nearby for using mingw cross-building packages on Ubuntu Linux. Both of these produce lots of standalone usable binaries installable as a typical NUT directory tree, which (with copies of DLLs for thi...

...un > without crashing on Windows - e.g. usbhid-ups and nut-scanner did see my > test UPS. Fixes originally made for libusb-0.1 were applied to libusb1.c > too, but not tried yet. > > Builds are possible, mostly scripted and documented, see: > > * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) > natively on Windows, > * `scripts/Windows/README` and a build script nearby for using mingw > cross-building packages on Ubuntu Linux. > > Both of these produce lots of standalone usable binaries installable as a > typical NUT directory tree, which...

...un > without crashing on Windows - e.g. usbhid-ups and nut-scanner did see my > test UPS. Fixes originally made for libusb-0.1 were applied to libusb1.c > too, but not tried yet. > > Builds are possible, mostly scripted and documented, see: > > * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) > natively on Windows, > * `scripts/Windows/README` and a build script nearby for using mingw > cross-building packages on Ubuntu Linux. > > Both of these produce lots of standalone usable binaries installable as a > typical NUT directory tree, which...

...on Windows - e.g. usbhid-ups and nut-scanner did see my >> test UPS. Fixes originally made for libusb-0.1 were applied to libusb1.c >> too, but not tried yet. >> >> Builds are possible, mostly scripted and documented, see: >> >> * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) >> natively on Windows, >> * `scripts/Windows/README` and a build script nearby for using mingw >> cross-building packages on Ubuntu Linux. >> >> Both of these produce lots of standalone usable binaries installable as a >> typical N...

...on Windows - e.g. usbhid-ups and nut-scanner did see my >> test UPS. Fixes originally made for libusb-0.1 were applied to libusb1.c >> too, but not tried yet. >> >> Builds are possible, mostly scripted and documented, see: >> >> * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) >> natively on Windows, >> * `scripts/Windows/README` and a build script nearby for using mingw >> cross-building packages on Ubuntu Linux. >> >> Both of these produce lots of standalone usable binaries installable as a >> typical N...

...d-ups and nut-scanner >>> did see my test UPS. Fixes originally made for libusb-0.1 were applied to >>> libusb1.c too, but not tried yet. >>> >>> Builds are possible, mostly scripted and documented, see: >>> >>> * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) >>> natively on Windows, >>> * `scripts/Windows/README` and a build script nearby for using mingw >>> cross-building packages on Ubuntu Linux. >>> >>> Both of these produce lots of standalone usable binaries installable as...

...d-ups and nut-scanner >>> did see my test UPS. Fixes originally made for libusb-0.1 were applied to >>> libusb1.c too, but not tried yet. >>> >>> Builds are possible, mostly scripted and documented, see: >>> >>> * `docs/config-prereq.txt` and `ci_build.sh` for MSYS2 (includes MinGW) >>> natively on Windows, >>> * `scripts/Windows/README` and a build script nearby for using mingw >>> cross-building packages on Ubuntu Linux. >>> >>> Both of these produce lots of standalone usable binaries installable as...

...allation) and let me know all seems okay before I merge it :) Especially for devices that reported such data well with the original NUT codebase :) It would probably go along the lines of: :; cd /tmp :; git clone -b issue-1279 https://github.com/jimklimov/nut :; cd nut :; INPLACE_RUNTIME=true ./ci_build.sh ### Temporarily stop your original drivers :; ./drivers/nutdrv_qx -a DEVNAME_FROM_UPS_CONF -d1 # -x override...=... ### Can start back your original drivers Options set by that user who cooperated in testing, for the device which reported insufficient data on its own: driver.parameter.batter...