Skip to content
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.

Using MobileFFmpeg in Commercial Applications

Taner Sener edited this page Oct 29, 2018 · 7 revisions

It is possible to use MobileFFmpeg in commercial applications but there are licensing conditions that must be met depending the version used.

First of all, please note that all binaries except IOS universal static binaries are dynamically linked. IOS universal static binaries are prebuilt binaries with -ios-static-universal postfix or binaries built by providing --static flag to ios.sh build script.

  • Dynamically linked LGPL libraries of MobileFFmpeg can be safely used in a commercial applications. In this using scheme, commercial application will have its own license and mobile-ffmpeg will be licensed under LGPL. Dynamic linking allows that. You need to only include detailed MobileFFmpeg LGPL License in your applications licensing documentation.

  • When Statically linked LGPL libraries are used, commercial application will be licensed under LGPL. So all conditions defined by LGPL must be met. This means you must provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the commercial application. It is hard to provide an application in an object format to allow relinking, so most of the users prefer providing source code of their application.

  • If GPL libraries are used, either dynamically or statically linked, commercial application will be licensed under GPL, all conditions defined by GPL must be met. This means you must make the source code available to the users of your commercial application as described in the GPL, and they must be allowed to redistribute and modify it as described in the GPL.

Clone this wiki locally