Last time we had some discussions in the libusb mailing list about using MinGW-w64 to build 64bit libusb-1.0 Windows backend.
http://libusb.6.n5.nabble.com/PATCH-28-37-core-now-references-windows-backend-td8410i80.html#a1046006 One issue we found is that recent version of libtool is needed to recognize 64bit library. The other issue is that libtool seems to point to x86_64-w64-mingw32\lib64 directory. And right now the released MinGW-w64 binaries has the real libraries inside x86_64-w64-mingw32\lib directory and only a few files inside x86_64-w64-mingw32\lib64 directory. So the following errors will happen. *** Warning: linker path does not have real file for library -lsetupapi. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libsetupapi but no candidates were found. (...for file magic test). ... The solution is to move the files inside lib64 to lib, change lib64 to be a symbolic link to lib (under Linux) or just copy all the files inside lib directory to the lib64 directory. What is the proper solution for this problem? Is this a libtool problem or MinGW-w64 packaging problem? -- Xiaofan ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
