On Sun, Sep 19, 2010 at 9:03 AM, JonY <jo...@users.sourceforge.net> wrote:
>> 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.

Sorry I do not quite understand you. I do not want the usb.h
from MinGW-w64.

MinGW-w64 is not really following MS. MSVC's own include directory
does not have usb.h and other files. Instead, they are using
the Windows SDK's include directory which may or may not have
usb.h.

For example, I just checked my VS2008/VS2010 installations, they install
bundled Windows SDK in a separate directory (Program Files\Microsoft SDKs\)
and I am not seeing the usb.h file in the bundled Windows SDK
directory (checked 5.0, 6.0a and 7.0a).

I have not installed standalone SDKs to know if they have usb.h or
not. Even if they have, it is in a separate directory from MSVC.
Windows DDK/WDK does have usb.h inside inc\api directory.


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