digging into libftdi situation I identified an issue
in: ${LIBFTDI_SRC}/cmake/Toolchain-${HOST_TRIPLET}.cmake
where CMAKE_FIND_ROOT_PATH is hardcodedI'm trying a workaround in: #6992 <https://review.openocd.org/c/openocd/+/6992> : [WIP] github workflow: use libusb 1.0.26 and hidapi 0.11.2 => github action finished without issues, but I need to test further (please refer to https://github.com/tarek-bochkati/openocd/actions/runs/2409477180 ) Regarding native MYS2 mingw32, I avoided that due to build time and because in it introduces more dll dependencies. Le sam. 28 mai 2022 à 04:01, Xiaofan Chen <xiaof...@gmail.com> a écrit : > Yes the update is good. > > Just wondering if you can revisit the situation of libftdi cross-build > again since > it has been removed due to issues. > > Then I also want to understand that why you do not want to switch to native > MYS2 mingw32/mingw64 build as it has built-in packages for libusb, hidapi > and libftdi which are pretty much up to date. > > Best regards, > Xiaofan > > On Wed, May 25, 2022 at 8:06 PM Tarek BOCHKATI <tarekbouchk...@gmail.com> > wrote: > > > > Thanks Xiaofan for the heads up. > > > > I updated 2 days ago the versions of both libusb1 to 1.0.26 and hidapi > to 0.11.2 > > > > this was tested in > https://github.com/tarek-bochkati/openocd/actions/runs/2371415845 > > > > > > please check: https://review.openocd.org/c/openocd/+/6992 > > > > > > -- > > > > Tarek > > > > >
