New implementation of udpsrc with many new features.

Original commit message from CVS:

New implementation of udpsrc with many new features.
parent 0d0ff109
Erik Walthinsen <>
Matt Howell <>
Brent Bradburn <>
Wim Taymans <>
Richard Boulton <>
Zaheer Merali <>
David I. Lehn <>
Chris Emerson <>
Jens Thiele <>
Thomas Nyberg <>
Bastien Nocera <>
Christian Fredrik Kalager Schaller <>
Thomas Vander Stichele <>
Andy Wingo <>
Cameron Hutchison <>
This source diff could not be displayed because it is too large. You can view the blob instead.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `' is used to create `configure' by a program
called `autoconf'. You only need `' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
Installation Names
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
`configure' recognizes the following options to control how it
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
Print a summary of the options to `configure', and exit.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
GStreamer is developed under the terms of the LGPL (see LICENSE file for details). Some of our plugins however rely on libraries which are available under i 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 or derived plugins.
When using GPL linked plugins GStreamer is for all practical reasons under the GPL itself.
The plugins which use a GPL library are as follows:
cdparanoia libcdparanoia (
aasink aalib (
xmms libxmms (
decdvd ac3dec,mpeg2dec (,
sidplay libsidplay (
Plugins derived from GPL code are as follows:
synaesthesia synaesthesia (
Plugins which use library a LGPL are as follows:
Colorspace Hermes (
httpsrc libghttp (
alsasink alsa (
aRts aRts (
sdlsink libsdl (
gnomevfssource gnome-vfs (
gnomevfssink gnome-vfs
esdsink libesd (
icastsend libshout (
lame libmp3lame (
gst1394 libraw1394 (
flac libFLAC (
RTP ortp (
Effectv effectv (
ffmpeg ffmpeg (
Plugins which use a BSD covered library are as follows:
vorbisenc libogg/libvorbis (
vorbisdec libogg/libvorbis
Plugins based on libraries with other free licenses:
xsink libXv (MIT X11 / X Consortium license)
gsm libgsm (MIT license
Plugins using non-free libraries:
xamp3 decoder libxaudio (
wincodec win32ddl (
SUBDIRS=gst-libs \
gst sys $(EXT_DIR) \
tools \
testsuite \
po \
DIST_SUBDIRS=ext gst-libs \
gst sys \
examples \
tools \
gconf \
testsuite \
po \
EXTRA_DIST=gst-plugins.spec depcomp \
ChangeLog common m4
rm -rf `find $(distdir)/common -name CVS`
rm -rf `find $(distdir)/m4 -name CVS`
This is gst-plugins, a set of plug-ins for GStreamer.
- make sure you compiled and at least did a test-run of GStreamer (core)
- check output of ./configure --help to see if any options apply to you
- configure the source tree:
- if you installed GStreamer, then do:
If configure complains about missing GStreamer, you should try
./configure --with-pkg-config-path=prefix/lib/pkgconfig
where prefix should be replaced by the prefix you used to configure
GStreamer. (Be mindful NOT to ADD a trailing / to that option !)
If this doesn't fix it, you have other issues ;)
- if you didn't install GStreamer, you can still compile the plug-ins.
Add the path to gstreamer-uninstalled.pc (which lives in the gstreamer
source tree) to PKG_CONFIG_PATH
or run configure --with-pkg-config-path=(path to gstreamer uninstalled)
- the output of configure will give you a list of plug-ins with external
dependencies (ie, depending on other libs, see below). By no means
should you try to get them all built on your first run. This is hard
enough as it is ;) Resist the urge to get the most features for now.
It doesn't list all of the non-depending plug-ins, which get built
regardless (unless you explicitly asked it not to).
- build the tree:
If any plug-in causes a problem at this stage, you should re-configure
with --disable-(dependency)
and doublecheck if configure reports this plug-in as being disabled.
Then re-run make.
- install:
- if you installed GStreamer, and want to install the plug-ins as well, run
make install
and, as root, run
- if you installed GStreamer, but don't want to install the plug-ins, run
gst-register --gst-plugin-path=.
- if you didn't install GStreamer, then do
path/to/gstreamer/tools/gst-register --gst-plugin-path=.
(Replace path/to/gstreamer obviously)
- test:
- run
gst-launch sinesrc ! fakesink
and prefix gst-launch with the path to gstreamer/tools if you didn't install
If this doesn't give any errors, you can abort it.
- try replacing fakesink with your choice of
osssink/esdsink/artsdsink/alsasink/jacksink (depending on what output
method you have available) and see if you hear a C tone.
- After this, you should look into installing an application, like
gst-player, gst-editor or monkey-media with rhythmbox.
When building from CVS sources, you will need to run to generate
the build system files.
GStreamer is cutting-edge stuff. To be a CVS developer, you need
what used to be considered cutting-edge tools.
ATM, most of us have at least these versions :
* autoconf 2.52 (NOT 2.52d)
* automake 1.5
* libtool 1.4 (NOT Gentoo's genetic failure 1.4.2)
* pkg-config 0.8.0 will check for these versions and complain if you don't have
them. You can also specify specific versions of automake and autoconf with
--with-automake and --with-autoconf
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.
You will probably have to pass at least --with-pkg-config-path to
to point to the CVS version of GStreamer.
When you have done this once, you can use to re-autogen with
the last passed options as a handy shortcut. Use it.
After the stage, you can follow the directions listed in
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.
When using GPL-linked plug-ins, GStreamer is for all practical reasons
under the GPL itself.
The plug-ins which use a GPL library are as follows:
cdparanoia libcdparanoia (
aasink aalib (
xmms libxmms (
decdvd ac3dec,mpeg2dec (,
mad mad (
Plug-ins which use an LGPL library are as follows:
colorspace Hermes (
httpsrc libghttp (
alsasink alsa (
arts aRts (
sdlsink libsdl (
gnomevfssource gnome-vfs (
gnomevfssink gnome-vfs
esdsink libesd (
icastsend libshout (
lame libmp3lame (
gst1394 libraw1394 (
flac libFLAC (
RTP ortp (
Plug-ins which use a BSD covered library are as follows:
vorbisenc libogg/libvorbis (
vorbisdec libogg/libvorbis
Plug-ins based on libraries with other free licenses:
xvideosink libXv (MIT X11 / X Consortium license)
gsm libgsm (MIT license
Plug-ins using non-free libraries:
wincodec win32ddl (
GStreamer uses a *large* array of tools and libraries, most of which are
optional. We have attempted to make sure that any code that depends on
optional libraries doesn't get built unless you have those libraries. If
you find this not to be the case, please, let us know by filing a bug
report at
Required tools:
An extra set of tools is required if you wish to build GStreamer out of
CVS (using
autoconf 2.52 or better
automake 1.5
libtool v1.4 or better
pkgconfig 0.9.0 or better (
Required libraries:
The core GStreamer libraries. See the gstreamer/ module in GStreamer cvs, or
the version that corresponds to this plugin release.
Optional libraries:
This file lists supporting libraries for which gst-plugins contains plugins,
as well as their minimum version. You can find the corresponding plugins in
libHermes (for colorspace conversions; you need this for any video work)
libghttp (for httpsrc)
libaudiofile (for afsrc/afsink
libmad (for the mad mp3 decoder plugin)
libjpeg (for jpegenc/jpegdec)
libopenquicktime (for the QT plugin)
libXv (for videosink)
libxaudio (for xa mp3 decoder)
libvorbis (for vorbisenc, vorbisdec)
libcdparanoia (for cdparanoia ripper)
liblame (for lame mp3 encoder)
libshout (for the shoutcast plugin)
libasound (for the alsa src/sink plugin)
librtp (for the rtp sink plugin)
aalib (for the aa sink plugin)
aRts (for the arts plugin wrapper, and the artsd sink)
raw1394/linux1394 (for the dv plugin)
libdvdread (for the dvdsrc)
(optional: libcss for encrypted DVDs)
libdvdnav (for the dvdnavsrc)
(optional: libcss for encrypted DVDs)
>= 0.1.9
libesound (for the esd sink
gnome-vfs (for the gnome-vfs src)
>= 2.4.0
libgsm (for the gsm plugin)
sdl (for the sdl sink)
xmms (for the xmms plugins wrapper)
mpeg2dec/a52dec (for mpeg2 related plugins and dvd playback)
>= v0.3.1/v0.7.2
swfdec (for the swfdec plugin)
>= 0.2.0
flac (for the FLAC lossless audio format)
>= 1.0.3 preferred, 1.0.2 should work
gtk (for the gdk_pixbuf plugin)
>= 2.2.1 preferred, 2.0 ok
pango (for the textoverlay plugins)
Optional debian packages: