Re: Re: [fluid-dev] W =?ISO-8859-1?Q?indows Sound Output -?= directsound (dsound.h)

[list]

Thanks for your interest.

Please take care with the license when handling microsoft code and wine
or other software. By downloading the SDK you already agreed to their
license. I am not exactly sure what is allowed and what not, but if
there is improvement for wines dsound.h in the end please respect the
rules of clean room reverse engineering.

I think you  can submit dsound.h fixes and you can look at the ms
dsound.h but shouldn't directly copy functions and data structures "but
in wine they need to  be similar; the spacing and indentation can
differ." (Last is a quote from the wine irc channel)

This is a quote from the Winedevs, too:
"The stuff in headers is not really protected and we can add similar
stuff to our headers nothing really disallows you from copying data
structures or functions but don't copy comments and try to keep the
coding style different (in general ms headers are ugly)"

about the problem:

We build with GUB, and this is how we do it:
http://github.com/janneke/gub/blob/master/gub/specs/fluidsynth.py

Attached is the dsound.h we use.

Nils

Am 28.11.2009 um  Uhr haben Sie geschrieben:
> Hello Nils,
>
> Quoting Nils <address@hidden>:
> > Hey fluidsynths,
> >
> > for our Denemo Windows sound-output we use fluidsynth.
> > I compiled fluid with dsound.h from WINE (and with portaudio).
> >
> > Dsound is not working. I have to test if it does work with the
> > official directX SDK dsound.h but I don't want to agree to their
> > license you need for downloading, so maybe you have more experience
> > here?
> >
> > Nils
> >
>
> Could you point me to a copy of the dsound.h you are using or attach
> it?  I tried using a wine dsound.h before, but it had some
> dependencies and I didn't really get past the build stage.  I have the
> SDK installed and can test with it and then try your dsound.h.
>
> Josh
>
>
>

dsound.h
Description: Text Data