Hi, We are currently using a multilib MinGW-w64 to generate 32 and 64 bit binary snapshots for the libusb 1.0 Windows backend. This includes static libraries as well as DLLs, with the latter being built with the aim of being fully interchangeable with MSVC/WDK ones (which we can also build in our project).
Apart from the issue reported yesterday (which we've already worked around), we haven't seen major issues linked to using a multilib MinGW-w64 instead of MinGW32. However, the FAQ on multilib seems to indicate that it is "still under construction" [1], and while the multilib feature seems to be prominently advertised, as well as enabled by default by MinGW-w64's configure, there seems to be mixed messages as to whether it should be used or not. Some people on our list are actually very nervous about using it at all to produce any 32 bit binaries. From what I could see however, all the known multilib issues are currently closed [2]. Before we commit to continuing using multilib then, do you know any good reason why the use of multilib should be discouraged with MinGW-w64 at the moment? Regards, /Pete [1] http://sourceforge.net/apps/trac/mingw-w64/wiki/Answer%20Multilib%20Toolchain [2] http://sourceforge.net/search/?group_artifact_id=983354&type_of_search=artifact&group_id=202880&words=multilib ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
