Re: dsound: Use wine dxguid rather then mingw dxguid

[Roderick Colenbrander]

On Thursday 16 August 2007 12:06, Maarten Lankhorst wrote:
> Makes it cross-compilable to produce a windows binary.

I don't think this is the right way. It appears that native dxguid doesn't 
define some of the uuids needed for directdraw / directsound. You need to 
check where the missing guids are defined on windows.

In case of ddraw IDirectDraw3 stuff is in ddrawex.h whereas we define it in 
ddraw.h. Something similar could be the case for directsound.

Roderick

dsound: Use wine dxguid rather then mingw dxguid

[Maarten Lankhorst]

Roderick Colenbrander schreef:
> On Thursday 16 August 2007 12:06, Maarten Lankhorst wrote:
> > Makes it cross-compilable to produce a windows binary.
>
> I don't think this is the right way. It appears that native dxguid doesn't 
> define some of the uuids needed for directdraw / directsound. You need to 
> check where the missing guids are defined on windows.
>
> In case of ddraw IDirectDraw3 stuff is in ddrawex.h whereas we define it in 
> ddraw.h. Something similar could be the case for directsound
> I tried MS Platform SDK for win2003, but it doesn't have it, the missing
> IDS only exist in the DDK, and are not part of dxguid. The IID's are:

IID_IDsDriverNotify
IID_IDsDriverPropertySet

It's part of wine's way of calling device drivers. Only other way would
be to include initguid.h once in dsound and winealsa/wineoss. I'm not
sure which of the two is preferred.

Cheers,
Maarten

dsound: Use wine dxguid rather then mingw dxguid

[Alexandre Julliard]

Maarten Lankhorst <m.b.lankhorst(a)gmail.com> writes:
> I tried MS Platform SDK for win2003, but it doesn't have it, the missing
> IDS only exist in the DDK, and are not part of dxguid. The IID's are:

If the ids are not in the PSDK libdxguid then they shouldn't be in the
Wine one.

-- 
Alexandre Julliard
julliard(a)winehq.org