Hi,

I meant FFmpeg library (not application) in both questions.
Also I updated question 1. Hope is more clear now.

Thank you,
Ioan

1.      Let’s suppose that I own a library named "a.dll" that is linked 
statically or dynamically with FFmpeg library. Another library owned by me and 
named "b.dll" is linked dynamically with "a.dll". A plug-in based application 
owned by me and named "App.exe" uses "b.dll" as a plug-in (loads the plug-in at 
runtime).
In this scenario does  "a.dll", "b.dll" or "App.exe" become under LGPLv2.1 or 
later ? Does the source code corresponding to "a.dll", "b.dll" and "App.exe" 
become under LGPLv2.1 or later ?
In case the answer is yes, which of these libraries/executable becomes under 
LGPLv2.1 or later ? Which part of the source code owned by me and used to 
compile above libraries become under LGPLv2.1 or later?

Best regards,

Ioan Stan    senior software developer

 T : [ro] +40 3645 607 20; [de] +49 89 2154 892 20
E : [email protected]

München  |  Cluj Napoca  |  Oradea  |  www.accesa.eu

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Carl Eugen Hoyos
Sent: Wednesday, December 11, 2013 5:47 PM
To: [email protected]
Subject: Re: [Libav-user] Licensing question

Ioan Stan <Ioan.Stan@...> writes:

> 2.
> Also, if we want to provide, together with our application, a
> not-modified copy of FFmpeg, took from your FFmpeg’s web page or
> compiled and linked by us, can our work still be considered a “work
> that uses the library”  ?

IANAL.

Do you mean FFmpeg or ffmpeg?

If you mean ffmpeg (the application) and if your application is not linked to 
libavcodec etc. but if your application simply calls ("exec") ffmpeg, then none 
of the usual obligations are relevant for your application.
Don't forget that if you distribute ffmpeg (the application) you are 
responsible for providing the exact source code you used to compile the 
executable (we do not offer executables, you therefore cannot download them 
from FFmpeg's web page) and you have to make sure that your users know that 
ffmpeg was installed and under which license it was installed. (Please don't 
claim that you "own" FFmpeg, we read this in practically every EULA.)

Concerning "not-modified" (just to make 100% sure): You have the right to 
modify FFmpeg, it makes no difference if you modify it or not. (I am just 
adding this because some people seem to believe that it does make a difference 
and your question could imply that you also think so.)

Concerning your first question: I suspect it also contains a typo, at least I 
cannot parse it, please try to ask again with a little more information.

Carl Eugen

_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user

Reply via email to