Recompiled libmcp2221 with mingw 53_32, to prevent this compiler erro…
…r in Qt 5.11.1 programs:
libmcp2221.dll: file not recognized: File format not recognized collect2.exe: error: ld returned 1 exit status
Added dependencies for libmcp2221 from here: https://github.com/signal11/hidapi/blob/a6a622ffb680c55da0de787ff93b80280498330f/hidapi/hidapi.h https://github.com/signal11/hidapi/blob/a6a622ffb680c55da0de787ff93b80280498330f/windows/hid.c
Corrected some documentation in libmcp2221.h
Hmm, I would rather find out the root cause of the issue. If I release a new dll it will just stop working again. The 1.0.4 .dll provided in this repo was compiled with GCC 4.9.3, older versions were compiled with some older version.
I've just checked all the commits in the git repository. It looks to me there are 3 versions of the .dll/.a in lib/win. These are the first version: https://github.com/zkemble/libmcp2221/tree/58241a5085a835d1926bb4d7463dff2e04eb2c12/lib/win https://github.com/zkemble/libmcp2221/tree/5573162d563b07c0730bfb069771a07654323d1a/lib/win
These are the second version: https://github.com/zkemble/libmcp2221/tree/88fb4f4c960ac945ac7ba0954c67c044cf9ba7c0/lib/win https://github.com/zkemble/libmcp2221/tree/165cc68b8c61191b9f8010864b13f9ac43b4ef93/lib/win https://github.com/zkemble/libmcp2221/tree/f2a0da524e3d8af36d4c0b62a87a9be44797bac5/lib/win https://github.com/zkemble/libmcp2221/tree/965fe721fecd4e4c7594e97269a02c9d6e2779ea/lib/win https://github.com/zkemble/libmcp2221/tree/86e33eb19055aa581076f2e33f167ea570d2e5bd/lib/win https://github.com/zkemble/libmcp2221/tree/a52eb0d4acf038d1ad56a478e3cff45e4dbd8df0/lib/win https://github.com/zkemble/libmcp2221/tree/021bcd5973a83fb58ffa8fdf020b57157c10f456/lib/win
This is the third version: https://github.com/zkemble/libmcp2221/tree/54b04e4526ef786744bde26f879aa4aa3a62b101/lib/win
I find it strange that the .dll and the .a file don't change when the sourcecode does change. Could it be the .dll and .a file were not updated when new code was checked in?
Usually, I only update binaries when I make a new release (there's only been 3 releases). There's been no changes since v1.0.4 release, so both the source code and binaries are currently up to date.