Livecode's CEF Builds

[Monte Goulding]

There’s some questions here that need a lawyer to answer. 

To start with I think you need to ensure that building CEF with proprietary codecs enabled does not include anything that has a license that is incompatible with GPL 3. Otherwise you can’t distribute your standalone with the modified CEF under the GPL 3. FWIW I have built CEF with proprietary codecs and due to the complexity of chromium I would still need to spend a few days reviewing code to know exactly what was included when I did that. I do know there’s OpenH264 in there which is BSD licensed.

Then there’s whether the patents infringe on the GPL…  ¯\_(ツ)_/¯

FWIW if you can satisfy yourself that you aren’t infringing the GPL distributing the standalone with CEF built with proprietary codecs enabled then you should just be able to add some notes about that to include with your source like you would note that when distributed as a standalone it includes the LiveCode engine and where to find the source and build instructions for that etc… although again IANAL.

Cheers

Monte

> On 11 Sep 2018, at 10:48 am, Tom Glod via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> So I got a msg back and they are totally down with me shipping the codec as
> long as I pay the fees for the # of licenses I sell past 100,000
> 
> Correct me if I am wrong, can I not put the code of my application on
> github as GPL 3?  and build my standalones using LC with the modified CEF
> files ?
> 
> If someone builds from the standalones on github they get the full
> application except the avc / h264 codec in CEF?
> 
> Which license agreement does that break?
> 
> Is it also not an option to have community version and then a non-community
> version like LC does?  I am really down for paying the 40 cents or 25 cents
> per paid user whatever it is.
> 
> Is there any way to this work and still put my .livecode file on github?
> ...but ship standalones with the modified CEF build?