On Mon, Sep 20, 2010 at 1:28 AM, Kai Tietz <ktiet...@googlemail.com> wrote: > The usb.h header is here in our platform headers as we need it for the > case that no ddk is installed and somebody wants to use winusb.h > header.
OK this is a very good reason. WinUSB is useful. And indeed using WinUSB will need to have access to usb.h. However, if you want to use winusb.h inside MSVC, you actually have to get WDK and point MSVC to various include directory of the WDK. > I admit that this header is part of wdm/ddk, but well, why > libusb names a header in a way they know that it collids with an > pdsk/ddk/wdm header? As I said, that is a legacy from the Linux days. And at that time, there was no MinGW-w64. > We can think about it to move this header into our psdk_inc directory, > but well, I am not sure if this is what other people would actual > help, which are using usb.h header. I will respect the decision you make. I will be happy if usb.h and friends are put inside the psdk_inc directory or the future <ddk> directory where they really belong to. But if you decide to keep the current way, then we have to educate our users to know the problem with MinGW-w64. One easy solution is to rename MinGW-w64 usb.h. -- Xiaofan ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
