>From the user list. On Fri, Jul 23, 2021 at 5:47 PM Xiaofan Chen <[email protected]> wrote: > > On Fri, Jul 23, 2021 at 3:54 PM R. Diez <[email protected]> wrote: > > ... > > This is the log from OpenOCD v0.11.0, but with the same libusb > > v1.0.24.11584: > > > > -------------------------------------------------------------------------------- > > [ 0.002000] [000003b4] libusb: debug [libusb_init] created default context > > [ 0.002000] [000003b4] libusb: debug [libusb_init] libusb v1.0.23.11397 > > > > But there is one important issue. Note that the libusb version that OpenOCD > > v0.11.0 > > reports is v1.0.23.11397 . I was surprised. > > > > I manually deleted libusb-1.0.dll and I got the expected error "cannot > > open shared object file". > > > > Then I placed the same libusb v1.0.24.11584 I have used with OpenOCD > > v0.10.0, but OpenOCD v0.11.0 kept saying it was using version > > v1.0.23.11397. > > > > Is it possible that OpenOCD v0.11.0 is opening the libusb DLL, but then > > using a statically-linked version instead? > > Very good findings. It seems to me you can not just change the > DLL with the github binary in this case. You may have to build > by your own. >
Looks like the github action is not building the correct Windows binary. It will be good to use dynamic linking so that the user can use updated DLLs whenever possible. -- Xiaofan
