2010/6/7 Henry N. <[email protected]>:
>  On 07.06.2010 09:20, Ozkan Sezer wrote:
>> On Mon, Jun 7, 2010 at 10:17 AM, Wolfgang Glas<[email protected]>  wrote:
>>> On 2010-06-07 08:52, Ozkan Sezer wrote:
>>>> On Mon, Jun 7, 2010 at 12:09 AM, Dmitrijs Ledkovs
>>>> <[email protected]>  wrote:
>>>>> On 6 June 2010 12:00, Ozkan Sezer<[email protected]>  wrote:
>>>>>> On Sun, Jun 6, 2010 at 1:37 PM, Wolfgang Glas<[email protected]>  
>>>>>> wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>>   I'm using GUID_DEVINTERFACE_USB_DEVICE in my windows code, which uses
>>>>>>> setupapi.dll. This declaration has been in ddk/usbiodef.h as of 
>>>>>>> mingw-w64-gcc-4.4.1
>>>>>>>
>>>>>>>   However this header seems to be gone in erecnt versions (I'm 
>>>>>>> currently on
>>>>>>> sezero gcc-4.4.5-20100527). Morevover I can't find 
>>>>>>> GUID_DEVINTERFACE_USB_DEVICE
>>>>>>> in any other header.
>>>>>>>
>>>>>>>   Does anybody have deper insights into this issue?
>>>>>>>
>>>>>>>   Ragards and TIA, Wolfgang
>>>>>> This is a problem in our way of providing ddk headers: We
>>>>>> do a svn-link to reactos headers, specifically to their
>>>>> Is the svn-link pinned to a particular revision on the 1.0 branch?
>>>> It is not.
>>>>
>>>>> (Stability&  reproducibility is important for packagers ;-) )
>>> I'd like to double the request for reproducability. From the packagers 
>>> viewpoint
>>> it would be better to stick to a hand-selected (and tested) snapshot of 
>>> upstream
>>> sources.
>>>
>>> Ozkan, will you provide us with a new snapshot once the missing header 
>>> problem
>>> is sorted out?
>>>
>>>   Best regards, Wolfgang
>>>
>> Well when things get sorted out, we can make a "ddk snapshot"
>> release. Would that be appropriate?
>
>  From user side this would be very welcome. It is very difficult to find
> the right ddk headers for a snapshot of mingw build.
> For such snapshot this test case should please produce no errors and no
> warnings:
>
>      PREFIX=.../W64_160271
>      TARGET=x86_64-w64-mingw32
>      GCC=$PREFIX/bin/$TARGET-gcc
>
>      echo "#include<ntddk.h>">check.c
>      $GCC -I$PREFIX/$TARGET/include/ddk -Wall -c -o check.o check.c
>
> --
> Henry N.
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

Well, the only solution I see here for the ddk-optional SDK is, that
we do a fork of it and have to maintain it by ourself. The only need
we would have here is a volunteer doing the manual merge and which
signs responsible to build up an testsuite for it.
We should keep in experimental branch the link to reactos-svn, but
replace the links in branches. When we found a volunteer for it, we
can proceed on this.

Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to