On Mon, Sep 20, 2010 at 6:48 PM, Spencer Oliver <[email protected]> wrote: > This code was added for cases where high speed support is not detected by > configure and BUILD_FT2232_HIGHSPEED is not defined. > > If this is failing it looks more like a autoconf issue - what is the output > of configure?
You are right. The different between the MinGW 32bit and MinGW-w64 64bit build is that the option is different. For MinGW 32bit build: /* Support FT2232H/FT4232HS with FTD2XX or libftdi. */ #define BUILD_FT2232_HIGHSPEED 1 For MinGW-w64 64bit build /* Support FT2232H/FT4232HS with FTD2XX or libftdi. */ /* #undef BUILD_FT2232_HIGHSPEED */ Looking at the config.h and I found out the problem. Not an OpenOCD problem at all. But rather it is due to the conflict between MinGW-w64 usb.h and libusb-win32.h. libftdi includes usb.h by default. Once I rename MinGW-w64 usb.h to other names and put in libusb-win32 usb.h file, everything is fine. Please refer to the following thread. http://www.mail-archive.com/[email protected]/msg01853.html (start the discussion) http://www.mail-archive.com/[email protected]/msg01883.html (maybe end of discussion) I tried to convince MinGW-w64 people they should put their usb.h in include\ddk\usb.h just like MinGW, but seems they would not accept my proposal. This is rather unfortunate as it affects all projects using libusb-win32, including libftdi and OpenOCD. To rename MinGW-w64 usb.h to a different name is only a temporary solution. Any other better suggestions for this issue? -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
