Re: Possible To Use SDL2 & Android Studio 2 On Linux?

Eric Wing <[email protected]> Tue, 24 Jan 2017 10:02:05 -0800
Newsgroups gmane.comp.lib.sdl
Message-ID <CA+Q62MAD8tVkyqdE89eG6COtp_AGQXPNZeYunzkbowFuPT+GKg@mail.gmail.com>
On 1/23/17, Daniel Gibson <[email protected]> wrote:
> On 23.01.2017 19:22, Eric Wing wrote:
>> On 1/23/17, Daniel Gibson <[email protected]> wrote:
>>>
>>> One thing I wondered about is: You mention iOS support, but the license
>>> is LGPL - isn't LGPL incompatible with iOS?
>>> At least I think that this is a reason openal-soft isn't available on
>>> iOS.
>>
>> So Apple ships their own OpenAL version with Mac and iOS, so there are
>> no license issues with that.
>>
>> ALmixer was originally written in 2002-ish, back when SDL was LGPL. It
>> seemed like a good idea at the time. Oops.
>>
>> I've been going through a relicensing thing for awhile now. I haven't
>> promoted it mostly because I'm not fully done, but basically I'm
>> moving towards zlib like SDL is now.
>
> Cool!
>
>>
>> So for iOS, as long as you use the Core Audio decoder (default for Mac
>> & iOS), you are good (since I wrote that and rewrote the shim
>> interfaces for it...don't use SDL_sound).
>>
>> The .wav and .ogg codec I pulled from SDL_sound which is LGPL which is
>> why the migration isn't complete.
>
> I gotta admit I'm surprised SDL_sound is (still) licensed under LGPL,
> but maybe relicensing is hard due to external contributions?
>
>>
>> I have native Android OpenSL ES, Windows Media Foundation, and Apple
>> Core Audio decoders, so I can mostly avoid these codecs except on
>> Linux, which is already a bag of LGPL and dynamic linking, so it's not
>> a big problem there.
>>
>> Anyway, if you want to use ALmixer on iOS with the Core Audio codec, I
>> won't go after you. :)
>
> Good to know :)
>
>>
>> (If somebody wants to help me and get a zlib-like implementation for
>> these 2 codecs, I would appreciate it. This could either be a rewrite,
>> or Ryan Gordon determining that those codec parts were written by him
>> and relicensing it under zlib. I've been meaning to follow up with him
>> about this, but it keeps falling to the bottom of my list.)
>
> At least libogg and libvorbis and libvorbisfile are under BSD license;
> there is also stb_vorbis which is public domain.
> The "glue" to ALmixer would have to be rewritten, but it doesn't seem to
> be that much code..
> For decoding wav https://github.com/nothings/single_file_libs#audio
> lists some single file headers under liberal licenses (no idea how good
> those are).
>

Yeah, I've actually written to the Ogg Vorbis APIs before without
SDL_sound, and they were among the easier to use APIs. (In contrast, I
recall being very grumpy with Windows Media Foundation.) However,
since I've seen and worked with the SDL_sound Vorbis implementation
(in fact, I wrote the Ogg Tremor decoder based on it), I want to be
careful about the appearance of "contamination" since I've seen the
other implementation. So I'm kind of hoping somebody might volunteer
to help me and contribute one. It's been many, many years now since
I've looked at the implementation so maybe what I write will feel
perfectly clean.

As for WAV, stb is a pretty good idea. I was also thinking of just
borrowing directly from SDL now that it is zlib.

But time constraints and all, I'm kind of hoping I just get a
contributor, or Ryan just decides to re-license SDL_sound under zlib
(or at least just the parts I use), and then the problem is solved.

Thanks,
Eric