On Sun, Sep 19, 2010 at 6:44 PM, Ozkan Sezer <seze...@gmail.com> wrote: >> However, MinGW does not break existing software and puts >> those files inside include\ddk sub-directory. Why not >> MinGW-w64? > > What will happen to other software that expect usb.h > out of ddk subdirectory, then?
Please name one. And you can certainly include <ddk/usb.h>. Take note that MinGW has been out for years whereas MinGW-w64 is relatively new. And the users for MinGW-w64 will be most likely from MinGW users who want to create 64bit apps. Why not keep the existing include file structure whenever possible? -- 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
