<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
x264 is GPL, no doubt about that. I didn't check the bigger
library, but we'd definitely need to be able to indicate whether
it should be included or excluded.<br>
<br>
That brings up a bigger question: do we have fine-grained
control about which plugins get included or excluded as part of
the Android build? Do you support building *all* the plugins that
are available for Linux?<br>
<br>
Thanks,<br>
Gili<br>
<br>
On 05/10/2012 4:50 PM, Dragos D wrote:<br>
</div>
<blockquote
cite="mid:CAOAVqQ7QC=wFoeMk1p0b8+5NJmEnSPF-fO3LETNE-3HD54Wy3A@mail.gmail.com"
type="cite">
<p dir="ltr">My understanding is that ffmpeg is LGPL, but what
about x264? By the way, is it included in the big GStreamer
library? </p>
<div class="gmail_quote">On Oct 5, 2012 4:33 PM, "Sebastian Dröge"
<<a moz-do-not-send="true"
href="mailto:sebastian.droege@collabora.co.uk">sebastian.droege@collabora.co.uk</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fr, 2012-10-05 at 16:10 -0400, cowwoc wrote:<br>
> What's the impact of static linking followed by dynamic
linking as<br>
> you mentioned? I assume from a legal/LGPL point of view,
it's as if<br>
> we're dynamically linking our application with GStreamer,
correct?<br>
<br>
I'm not a lawyer but general understanding of LGPL and static
linking<br>
is, that you need to provide all means to be able to relink
the<br>
application against modified versions of the LGPL'd libraries.<br>
<br>
If you take a look at the approach we did for static linking
here you'll<br>
notice that this is absolutely nothing to worry about. All
(LGPL'd)<br>
GStreamer code is linked into a single shared library from
these static<br>
libraries and your application code is a) separate from this
and b) uses<br>
GStreamer and related libraries like a shared library, thus
the same<br>
rules apply as for using GStreamer as a shared library.<br>
<br>
E.g. the demo application I linked in the original mail
contains one<br>
shared library libgstreamer_android.so, which contains all of
GStreamer,<br>
dependencies, plugins. And another library libtutorial-5.so,
which<br>
contains the native code of the application.<br>
<br>
<br>
There should be no problem developing closed source,
commercial<br>
applications with this approach as it's the same situation you
have on<br>
desktop systems with shared LGPL'd libraries.<br>
<br>
_______________________________________________<br>
gstreamer-android mailing list<br>
<a moz-do-not-send="true"
href="mailto:gstreamer-android@lists.freedesktop.org">gstreamer-android@lists.freedesktop.org</a><br>
<a moz-do-not-send="true"
href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-android"
target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-android</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gstreamer-android mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-android@lists.freedesktop.org">gstreamer-android@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-android">http://lists.freedesktop.org/mailman/listinfo/gstreamer-android</a>
</pre>
</blockquote>
<br>
</body>
</html>