On 9/19/2010 08:00, Ozkan Sezer wrote: > On Sun, Sep 19, 2010 at 2:56 AM, Xiaofan Chen<xiaof...@gmail.com> wrote: >> On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezer<seze...@gmail.com> wrote: >>> On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen<xiaof...@gmail.com> wrote: >>>> I think the MinGW-w64 newly included usb.h will break >>>> many existing software which uses libusb-win32. For >>>> example, libftdi's header is called ftdi.h which includes<usb.h>. >>>> libusb and libusb-win32 have been around for years. >>>> Is it possible to move MinGW-w64 usb.h and associated >>>> files inside<ddk/>? >>> >>> AFAIK, usb.h is out of ddk because it is part of ms platform sdk, >>> therefore, it _needs_ to be out of a ddk subdirectory for proper >>> compatibility. >> > > For the record, what I am saying are not what we will or > will not do: I am am only saying how things should be (in > my opinions). > >> Then is it possible to put those file in include\sdks or >> includer\psdk or similar? > > All the headers provided under our include directory are > already part of sdk, therefore I don't know how a separation > can be possible. > > Admins? >
Personally, I think deviating from MS is a bad idea. If ms puts it in the normal psdk, so shall we. I guess libusb will have to use include_next if it wants the psdk usb.h. ------------------------------------------------------------------------------ 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
