[Openal] make error in under windows / cygwin
Sven Panne
Sven.Panne at BenQ.com
Tue Feb 7 02:03:56 PST 2006
No guns involved here... :-) While you have a look at it: Could you
please try to get rid of the global variables in the Windows backend?
grab_{read/write}_native can dynamically allocate what they need and
return a pointer to that data, which can be cleared up in
release_native. Alas, this is often a general problem in various
backends.
Cheers,
S.
________________________________
From: Jason Daly [mailto:jdaly at ist.ucf.edu]
Sent: Montag, 6. Februar 2006 17:58
To: Sven Panne
Cc: openal at opensource.creative.com
Subject: Re: [Openal] make error in under windows / cygwin
Sven Panne wrote:
Hmmm, after reading the waveformat audio docs on MSDN,
the Windows backend looks quite suspicious:
* The output device seems to be opened twice, but it is
only closed once.
* There is no call to waveOutReset before closing.
* The threading is far from clear to me, e.g. which
thread locks the mutex and which one unlocks it, if the device is used
synchronously or asynchronously, etc.
Well, I said it worked. I didn't make any statements about the
quality of the code (I didn't write it, either) ;-)
I haven't really changed the code, so all this was very
probably already the case before the build system changes.
Anyway, if I receive a fix soon it will be in the next
minor release, otherwise not. I don't think this backend should be a
blocking point...
Putting me under the gun, eh? All right, I'll see what I can do
:-) It would be good if all the backends at least worked properly
before the release.
--
--"J"
"I'm a castaway stranded in a desolate land,
I can see the footprints in the virtual sand."
--Neil Peart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://opensource.creative.com/pipermail/openal/attachments/20060207/9acb6a40/attachment-0001.html
More information about the Openal
mailing list