Closed tol-va closed 3 months ago
Ok, I worked around this issue and wanted to add my discovery. I have Arduino Sketch installed to work with the Nano board I'm using to convert the RC522 board's SPI to UART. I gave up on the linker, just dragging and dropping the files from the libusb project into the libnfc/busses/ directory resolved the missing header file issue. The path and build process of the libusb-win32 is not documented in that project. The next issue was the libusb0.dll. I tried using the dll in Windows32 that results from using the libusb-win32 installer. This did not work, so I searched my system to be sure I was pointing at the correct dll. This is when I discovered Arduino Sketch had added a copy of the libusb.dll to my driver store, System32\DriverStore\FileRepository\arduino_gemma.***\amd64\libusb0.dll. This is a much more accessible method of getting this driver.
After commenting out the pn53x specific files in the "\examples\CMakeLists.txt" file I was able to finish the windows build.
# pn53x-diagnose
# pn53x-sam
# pn53x-tamashell
The examples require the pn53x_transceive method from the "libnfc\chips\pn53x.h" file but there seems to be a failure to successfully link the classes even though the path looks correct, #include "libnfc/chips/pn53x.h". I'm good but I would suggest updating the Windows build documentation since the lusb0.dll from System32 did not successfully satisfy the build requirements. I'm on Windows 11.
I am on Windows 11 and I'm trying to build a dll for libnfc. It should work from what I can tell based on the Configure step passing in the GUI. I set the path variables in Powershell and then I ran CMake. When I try to build, a fatal error prevents the dll from being generated. Can you provide some insight into what I am doing wrong?
I added a wildcard to the src path to see if that would help.