On Tue, Sep 21, 2010 at 4:11 PM, Spencer Oliver <[email protected]> wrote: >>> If mingw-64 are already using usb.h then that creates a bit of a problem >>> for any interface that is expecting libusb usb.h. >>> >>> The only safe solution would be to use a subdirectory for libusb/libftdi >>> if mingw64 will not change their layout. >>> >> >> Even that may not be safe enough. For example libftdi's ftdi.h include >> <usb.h> and the compiler may use MinGW-w64's usb.h instead of >> libusb-win32 usb.h. >> > > I was thinking of putting the ftdi.h in the libusb directory as well. >
I see. This should work. Maybe an extra option to set the directory for libusb/libusb-win32's usb.h and libftdi's ftdi.h for the configure scripts will help. Similarly for the future when OpenOCD is moving to libusb-1.0 and libftdi-1.0, it is good to have an extra option to set the directory for libusb-1.0's libusb.h and libftdi-1.0's ftdi.h. -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
