2010/9/20 JonY <jo...@users.sourceforge.net>
> On 9/20/2010 22:09, Ozkan Sezer wrote:
> > On Mon, Sep 20, 2010 at 4:40 PM, JonY<jo...@users.sourceforge.net>
> wrote:
> >> On 9/20/2010 21:36, Earnie wrote:
> >>> Forgot to include the list.
> >>>
> >>> -------- Original Message --------
> >>> Message-ID:<4c976081.6090...@users.sourceforge.net>
> >>> Date: Mon, 20 Sep 2010 09:24:17 -0400
> >>> From: Earnie<ear...@users.sourceforge.net>
> >>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> >>> rv:1.9.1.13) Gecko/20100914 SeaMonkey/2.0.8
> >>> MIME-Version: 1.0
> >>> To: Kai Tietz<ktiet...@googlemail.com>
> >>> Subject: Re: [Mingw-w64-public] libusb-win32 usb.h and MinGW-w64
> >>> usb.h conflict
> >>> In-Reply-To:
> >>>
> >>> <aanlktin0lc8fvjywv9pn_-kvaa8sqa+hepdsctxsv...@mail.gmail.com<aanlktin0lc8fvjywv9pn_-kvaa8sqa%2bhepdsctxsv...@mail.gmail.com>
> >
> >>> X-Enigmail-Version: 1.0.1
> >>> Content-Type: text/plain; charset=ISO-8859-1
> >>> Content-Transfer-Encoding: 7bit
> >>>
> >>>
> >>>
> >>> Kai Tietz wrote:
> >>>> PS: I came to this by reading recent posts by Tor on mingw-users,
> >>>> where pointed out quite clear that mingw-w64 issues are a
> >>>> "non-subject" on mingw.org's ML.
> >>>>
> >>>
> >>> I hope that we can work together, I will speak up in favor of
> discussoin
> >>> of mingw-64 on the mingw.org's ML when I see this. I don't always
> join
> >>> in a conversation though due to lack of time/interest in the subject.
> >>> We also promote mingw-64 as the place for 64 bit binaries, but I
> >>> understand where you are coming from. Still, I would like to work with
> >>> you and not against you.
> >>>
> >>> Earnie
> >>>
> >>
> >> Good, the flames were getting a bit old. Ozkan, can you explain your
> >> recent change with winusb.h?
> >
> > I thought the patches were self-explanatory: usb.h doesn't live
> > under a ddk subdirectory and winusb.h doesn't need ddk, revisions
> > 3590/3591 fixed those issues.
> >
> > I really don't know how/what else to explain.
> >
> > --
> > Ozkan
> >
>
> 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
>
>
------------------------------------------------------------------------------
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
