[openal] OpenAL Soft 1.19.1 released!

[Chris Robinson]

On 10/15/18 3:52 AM, michael kapelko wrote:
> Hi.
> I'm probably out of sync, but what are the goals of splitting OpenAL Soft?
> Thanks.

For the most part, it'll provide reusable components for other uses, 
like implementing other APIs. Sometimes the OpenAL API isn't a good fit 
for a particular use-case, and more direct access to internals is 
desirable (taking on the additional responsibility of not doing things 
that can cause crashes or UB). Testing could also be easier, since test 
apps could poke directly at the low-level processing functions which are 
normally hidden from the DLL interface.

It will also allow quicker implementation of certain features, since it 
won't require designing a safe and stable OpenAL-like interface. Such an 
interface can still be made if it's a feature OpenAL apps would benefit 
from, it just won't hold up the low-level implementation.

On top of that, it will give me a way to audit the code to be able to 
relicense it. I can verify the code that gets moved into the lower level 
library is either mine, or I have permission to relicense. Anything I 
don't, I can rewrite as I move it in. Then I can ensure the 
OpenAL<->LowLevel API bridge is done fresh, and I can move away from the 
LGPL as needed.