Commit e5ea6c49 authored by Tim-Philipp Müller's avatar Tim-Philipp Müller 🐠

Automatic update of common submodule

From 3cb3d3c to 5edcd85
parent bd504e37
GStreamer is currently maintained by the consensus of a number
of people, including, but not limited to:
David Schleef <>
Jan Schmidt <>
Wim Taymans <>
Thomas Vander Stichele <>
Tim-Philipp Müller <tim centricular net>
Jan Schmidt <>
Wim Taymans <>
David Schleef <>
Tim-Philipp Müller <tim centricular net>
Sebastian Dröge <slomo circular-chaos org>
Maintainer-related issues should be addressed to:
GStreamer 1.1.x development series
This is GStreamer Bad Plug-ins.
This package is in the 0.9.x series. This means that this is a
development series leading up to a stable 0.10.x series.
You have been warned.
This is GStreamer, a framework for streaming media.
We have a website at
You should start by going through our FAQ at
There is more documentation; go to
You can subscribe to our mailing lists; see the website for details.
GStreamer 0.9 development series - Hung by a Thread
We track bugs in GNOME's bugzilla; see the website for details.
You can join us on IRC - #gstreamer on
GStreamer 1.0 series
......@@ -116,8 +133,22 @@ set of available plug-ins into four modules:
problem and send us a patch, or bribe someone into fixing them for you.
- New contributors can start here for things to work on.
- Linux is of course fully supported
- FreeBSD is reported to work; other BSDs should work too
- Solaris is reported to work; a specific sunaudiosink plugin has been written
- MacOSX works, binary 1.x packages can be built using the cerbero build tool
- Windows works; binary 1.x packages can be built using the cerbero build tool
- MSys/MinGW builds
- Microsoft Visual Studio builds are not yet available or supported
- Android works, binary 1.x packages can be built using the cerbero build tool
- iOS works
You should always prefer installing from packages first. GStreamer is
well-maintained for a number of distributions, including Fedora, Debian,
Ubuntu, Mandrake, Gentoo, ...
......@@ -126,13 +157,14 @@ Only in cases where you:
- want to hack on GStreamer
- want to verify that a bug has been fixed
- do not have a sane distribution
should you choose to build from source tarballs or CVS.
should you choose to build from source tarballs or git.
Find more information about the various packages at
- again, make sure that you really need to install from source !
If GStreamer is one of your first projects ever that you build from source,
consider taking on an easier project.
......@@ -143,34 +175,31 @@ COMPILING FROM SOURCE TARBALLS
to build GStreamer.
- if you want to install it (not required), run
- if you want to install it (not required, but what you usually want to do), run
make install
- You should create a registry for things to work.
If you ran make install in the previous step, run
as root.
If you didn't install, run
as a normal user.
- try out a simple test:
gst-launch fakesrc num_buffers=5 ! fakesink
(If you didn't install GStreamer, again prefix gst-launch with tools/)
gst-launch -v fakesrc num_buffers=5 ! fakesink
(If you didn't install GStreamer, prefix gst-launch with tools/)
If it outputs a bunch of messages from fakesrc and fakesink, everything is
If it did not work, keep in mind that you might need to adjust the
PATH and/or LD_LIBRARY_PATH environment variables to make the system
find GStreamer in the prefix where you installed (by default that is /usr/local).
- After this, you're ready to install gst-plugins, which will provide the
functionality you're probably looking for by now, so go on and read
that README.
When building from CVS sources, you will need to run to generate
When building from git sources, you will need to run to generate
the build system files.
You will need a set of additional tools typical for building from CVS,
You will need a set of additional tools typical for building from git,
- autoconf
- automake
......@@ -182,10 +211,7 @@ them. You can also specify specific versions of automake and autoconf with
Check options by running --help can pass on arguments to configure - you just need to separate them
from with -- between the two.
prefix has been added to but will be passed on to configure because
some build scripts like that. can pass on arguments to configure
When you have done this once, you can use to re-autogen with
the last passed options as a handy shortcut. Use it.
......@@ -193,22 +219,34 @@ the last passed options as a handy shortcut. Use it.
After the stage, you can follow the directions listed in
You can also run your whole cvs stack uninstalled. The script in
the gstreamer module /docs/faq/gst-uninstalled) is helpful in setting
up your environment for this.
You can also run your whole git stack uninstalled in your home directory,
so that you can quickly test changes without affecting your system setup or
interfering with GStreamer installed from packages. Many GStreamer developers
use an uninstalled setup for their work.
There is a '' script in
to easily create an uninstalled setup from scratch.
GStreamer is developed under the terms of the LGPL (see LICENSE file for
details). Some of our plug-ins however rely on libraries which are available
under other licenses. This means that if you are using an application which
has a non-GPL compatible license (for instance a closed-source application)
with GStreamer, you have to make sure not to use GPL-linked plug-ins.
under other licenses. This means that if you are distributing an application
which has a non-GPL compatible license (for instance a closed-source
application) with GStreamer, you have to make sure not to distribute GPL-linked
When using GPL-linked plug-ins, GStreamer is for all practical reasons
under the GPL itself.
The fundamental design comes from the video pipeline at Oregon Graduate
Institute, as well as some ideas from DirectMedia. It's based on plug-ins that
will provide the various codec and other functionality. The interface
GStreamer Static Linking README
DRAFT, April 2013
It is possible to link GStreamer libraries, plugins and applications
statically, both in case of free/libre/open-source software applications
and proprietary applications. On some platforms static linking may even
be required.
However, distributing statically linked binaries using GStreamer usually
requires additional effort to stay compliant with the GNU LGPL v2.1 license.
The purpose of this document is to draw attention to this fact, and to
summarise in layman's terms what we believe is required from anyone
distributing statically linked GStreamer binaries. Most of this also
applies to dynamically linked GStreamer binaries.
This document is not legal advice, nor is it comprehensive. It may use
words in ways that do not match the definition or use in the license
text. It may even be outright wrong. Read the license text for all the
details, it is the only legally binding document in this respect.
This document is primarily concerned with the implications for the
distribution of binaries based on LGPL-licensed software as imposed by
the LGPL license, but there may be other restrictions to the distribution
of such binaries, such as terms and conditions of distribution channels
(e.g. "app stores").
The GNU LGPL v2.1 license allows use of such-licensed software by
proprietary applications, but still aims to ensure that at least the
LGPL-licensed software parts remain free under all circumstances. This
means any changes to LGPL-licensed source code must be documented and
be made available on request to those who received binaries of the
software. It also means that it must be possible to make changes to the
LGPL-licensed software parts and make the application use those, as far
as that is possible. And that recipients of an application using
LGPL-licensed software are made aware of their rights according to the
LGPL license.
In an environment where GStreamer libraries and plugins are used as
dynamically-loaded shared objects (DLL/.so/.dyn files), this is usually
not a big problem, because it is fairly easy to compile a modified version
of the GStreamer libraries or LGPL plugins, and the application will/should
just pick up and use the modified version automatically. All that is needed
is for the original, LGPL-licensed source code and source code modifications
to be made available, and for a way to build the libraries or plugins for
the platform required (usually that will be using the build system scripts
that come with GStreamer, and using the typical build environment on the
system in question, but where that is not the case the needed build scripts
and/or tools would need to be provided as well).
* You must tell users of your application that you are using LGPL-licensed
software, which LGPL-licensed software exactly, and you must provide them
with a copy of the license so they know their rights under the LGPL.
* You must provide (on request) all the source code and all the changes
or additions you have made to the LGPL-licensed software you are using.
For GStreamer code we would recommend that the changes be provided either
in form of a branch in a git repository, or as a set of "git format-patch"-
style patches against a GStreamer release or a snapshot of a GStreamer git
repository. The patches should ideally say what was changed and why it
was changed, and there should ideally be separate patches for independent
* You must provide a way for users of your application to make changes to
the LGPL-licensed parts of the code, and re-create a full application
binary with the changes (using the standard toolchain and tools of the
target platform; if you are using a custom toolchain or custom tools
you must provide these and document how to use them to create a new
application binary).
Note that this of course does not mean that the user is allowed to
re-distribute the changed application. Nor does it mean that you have
to provide your proprietary source code - it is sufficient to provide a
ready-made compiled object file that can be relinked into an application
binary with the re-compiled LGPL components.
While most GStreamer plugins and the libraries they depend on are licensed
under the LGPL or even more permissive licenses, that is not the case for
all plugins and libraries used, esp. those in the gst-plugins-ugly or
some of those in the gst-plugins-bad set of plugins.
When statically linking proprietary code, care must be taken not to
statically link plugins or libraries that are licensed under less permissive
terms than the LGPL, such as e.g. GPL-licensed libraries.
1. Proprietary GStreamer/GLib-based Application On iOS
Let's assume an individual or a company wants to distribute a proprietary
iOS application that is built on top of GStreamer and GLib through
Apple's App Store. At the time of writing the Apple iPhone developer
agreement didn’t allow the bundling of shared libraries, so distributing
a proprietary iOS application with shared libraries is only possible using
distribution mechanisms outside of the App Store and/or only to jailbroken
devices, a prospect that may not appeal to our individual or company. So the
only alternative then is to link everything statically, which means the
obligations mentioned above come into play.
2. Example: Jabber on iOS
Tandberg (now Cisco) created a Jabber application for iOS, based on GStreamer.
On request they provided an LGPL compliance bundle in form of a zip file, with
roughly the following contents:
Jabber/libip.a [236MB binary with proprietary code]
Jabber/Resources/{Images,Audio,Sounds,IB,Message Styles,Emoticons,Fonts}/*
opensource/toolchain/darwin-x86/bin/{misc autotoools,m4,glib-mkenums,glib-genmarshal,libtool,pkg-config,etc.}
readme.txt starts with "This Readme file describes how to build the Cisco
Jabber for iPad application. You need to install Xcode, but the final package
is built by running" and describes how to build project,
prerequisites, the procedure in detail, and a "How to Include Provisioning
Profile Manually / Alternate Code Signing Instructions" section.
3. Random Links Which May Be Of Interest
common @ 5edcd857
Subproject commit 3cb3d3cbbf794c18a6f91866c6d7fa38880c1eb8
Subproject commit 5edcd857b2107cd8b78c16232dd10877513ec157
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment