Re: Lame encoding and licensing

Am Thu, 30 Apr 2020 06:44:19 +0000
schrieb Al Fransham at Affective Sound via Lame-dev <[email protected]>: 

> "[The decoding functions] may not be used by any program not released under the GPL unless you obtain such permission from the MPG123 project (www.mpg123.de)<http://www.mpg123.de)>."
> 
> So, if I only use the encoding functions from my code, is this a non-issue?

You probably should better ensure that the relevant code is not even
linked in. But this all would be rather moot if you used the attached
patch to replace the old mpg123 code in Lame with usage of libmpg123
(see http://mpg123.de, nowadays).

1. Install current mpg123 snapshot, build.
2. Apply attached patch to Lame svn (did not test relase).
3. autoreconf -iv
4. Configure and build Lame with external mpg123 usage.

You might have to set PKG_CONFIG_PATH to locate  the libmpg123.pc file
from mpg123. Then, Lame should pick up libmpg123 and you should see
frontend/lame being linked to it. Then, you're not using the ancient
GPL code from mpglib, but the LGPLed libmpg123.

I'm going for a release now … a RC in a few days, a proper release
somewhen in May, after we had some years now with the lame-related API
changes to make the attached patch possible lingering in the
development trunk. Mpg123 1.26.0 will contain the changes for the
libmpg123 usage from Lame to work. Maybe we manage to make a new Lame
release after that and finally get rid of this licensing confusion?


Alrighty then,

Thomas


_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev