2

I am currently writing a video project using FFMPEG shared library with other license abiding projects (like libass and freetype2). I have a script that compiles FFMPEG and the other libraries as a single .so file (Android) and then my actual code just imports/dynamic links the library and use its functions. I have FFMPEG code released the way I compiled it with the libraries on an open source platform (like Github) which I assume abides to the license.

FFMPEG is compiled without the "non-free" and "gpl" flags so everything together (including the other 3rd party libraries compiled with it) should be LGPL 2.1 (not GPL3). I plan to have it as a submodule to my video player project.

For my video player library, I do not planning on open sourcing (for reasons out of my control). If my video player is just loading the shared library at runtime can it be treated as its own license, can I can have my video player closed source and have different license? Supposedly anyone can take the library and compile their own shared library and load it into the app.

Improve this question
4
  • How are you distributing your closed source video player? Are you including the .so files or .dll files of FFmpeg in the same package as your video player?
    – Brandin
    Dec 18 '18 at 5:23
  • Closed source video player will be put on the Android playstore. It will include the .so files inside the app when distributed
    – user654628
    Dec 19 '18 at 19:53
  • did you compile with the flags mentioned in their list?ffmpeg.org/legal.html
    – Richard Barber
    Dec 22 '18 at 0:07
  • As I wrote in the post, i compiled everything to be LGPL which means I did not compile non-free or gpl stuff. Also again I am dynamically linking it
    – user654628
    Dec 23 '18 at 1:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.