On Mon, Sep 20, 2010 at 9:57 PM, Ozkan Sezer <seze...@gmail.com> wrote:
> On Mon, Sep 20, 2010 at 4:03 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:

>> In this case, MinGW is actually following MS side, and not MinGW-w64,
>> Even Kai Tietz admits that MinGW-w64 usb.h belongs to DDK. It is just
>> because of the convenience (to support winusb.h without DDK) that
>> it is put in the platform headers now. In my opinion, this might also have
>> something to do with the fact that MinGW-w64 does not have a stable
>> ddk header in the distribution right now (only in the experiment branch).
>>
>> I hope that MinGW do not change this one. <ddk/usb.h> is the right
>> place for usb.h for MinGW.
>
> You are misleading people by giving misinterpreted information:
> MS distributes the usb.h header only in their WDK package, yes,
> however the header do _not_ reside in a ddk subdirectory:  it
> lives among all other psdk headers within the wdk package.
> Since WDK is a standalone package, it has several directories
> holding different kind of headers, like "crt" for C runtime
> headers, "ddk" (for ddk obviously), and "api" which holds psdk
> headers plus some extra ones such as the usb.h, usb100.h,
> usb200.h, etc.  Therefore it would simply be a mistake to move
> it under a ddk subdirectory, it has to live among other psdk
> headers.

I am not saying you do not have a point. But even you agree
that it is "extra" to PSDK (now called SDK). So I do not
think I misinterpreted information. It is just different
interpretation.

Anyway, I will respect whatever the decision MinGW-w64 makes.




-- 
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

Reply via email to