On 9/21/2010 07:53, Xiaofan Chen wrote: > On Mon, Sep 20, 2010 at 10:30 PM, Ruben Van Boxem > <vanboxem.ru...@gmail.com> wrote: >> 2010/9/20 JonY<jo...@users.sourceforge.net> >>> OK, I see. I suppose some include_next tricks are in order for libusb. >>> >> >> Long time reader of this discussion :) >> Why not just add this to the bottom/top of libusb's usb.h header: >> >>> #ifdef __MINGW64_VERSION_MAJOR >>> >>> #include_next<usb.h> >>> >>> #endif // __MINGW64_VERSION_MAJOR > > Thanks. I am not familiar with include_next. In this case, > where should we ask the user to put libusb-win32's usb.h > file? In its own separate directory? And how to get > the compiler use libusb-win32's usb.h before > the MinGW-w64 usb.h? > >
libusb usb.h can live in its own dir. All that is needed is the proper -I. In libusb usb.h, use #include_next to include mingw-w64 usb.h. Its that simple. ------------------------------------------------------------------------------ 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
