Hello,
I see this is a very old issue. I see there's still the libusb10 branch in the repository. I was wondering why it hasn't been worked on in years. Do you have any news?

Hello,
@doegox worked on it few years ago, then we worked on other subject.
If you want to update this branch to finalize the switch you are more than welcome !
Feel free to fork libnfc and bring libnfc to libusb 1.0, we will be happy to merge it upstream and made a new major release.

please update libusb. I have trouble to run on Macos, neither ubuntu :(

You can use the compat version of libusb by installing it using mac port
sudo port install libusb-compat
sudo activate libusb-compat

It will make libnfc work

Hello,
Is there a way to get rid of libusbk when using a ACR-122U USB reader with libnfc.dll on windows ?

• with libusb1.0-libnfc ported on Windows, would we still need libusbK driver wrapper when using libnfc.dll on Windows ?
  (when I don't install libusbK on native ACR122U USB driver --> No NFC device found. ; with LibusbK --> NFC device: ACS / ACR122U PICC Interface opened )
  My goal is to be able to use nfc-tools (nfc-list, nfc-mfcclassic, ...) directly with (ACR122U) USB native driver

If anyone is interested, I've tested a solution:
cross compilation of libusb 1.0 then using this version in libnfc fork-libusb10, cross compiled to windows : more infos on my blog post here : http://legacy.averbouch.biz/libnfc-and-nfc-utils-binaries-on-windows-10/#libnfc-libusb10
https://blog.avxt.fr/libnfc-and-nfc-utils-binaries-on-windows-10/#libnfc-libusb10
The answer to my question seems to be : NO --> I still need LibUSBK driver to be able to use nfc-list.exe with my ACR122U
But, when I run libusb10/listdevs.exe the app sees ACR122U even without installing Libusbk driver wrapper. So I guess that the issue (ACR 122U not detected in Libnfc with native driver) comes from the ACR122_USB driver code in libnfc/driver/acr_122usb.c ...--> Is there anyone that can confirm that point please ?

below : test with libusb/listdevs.exe (with or without Libusbk, same detection OK)

below: test with nfc-list and libnfc-libusb10 (WITH LibUsbK installed)

dumpbin /EXPORTS libusb1-0.dll (to check if functions are really the 1.0 ones)

below dumpbin /EXPORTS libnfc_libusb10 to check list of functions

Switching to libusb1.0 would indeed be a favorable option.

Compiling this for iOS devices and the ARM Mac has been a pain as somehow it's still relying on the compat layer, which honestly isn't that much of a problem but still shouldn't be there when a better libusb is available. Would make sense to migrate away from the old library at this point.