...
 
Commits (15803)

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.

......@@ -2,17 +2,13 @@ aclocal.m4
autom4te.cache
config.h
config.h.in
config.h-new
config.log
config.status
config.guess
config.sub
config.rpath
configure
gst-plugins.spec
gstreamer-libs-uninstalled*.pc
gstreamer-libs*.pc
gstreamer-play-uninstalled*.pc
gstreamer-play*.pc
libtool
stamp-h
stamp-h.in
......@@ -26,4 +22,47 @@ install-sh
depcomp
autoregen.sh
ABOUT-NLS
/INSTALL
_stdint.h
gst-plugins-good-*.tar.*
.dirstamp
/m4
.deps
.libs
*.lo
*.la
*.o
Makefile.in
Makefile
*~
*.swp
*.gc??
/m4
/ext/dv/smpte_test
/gst/multifile/test-splitmux-part-reader
/gst/deinterlace/tvtime.h
tmp-orc.c
*orc.h
/tests/examples/jack/jack_client
/tests/examples/rtsp/test-onvif
Build
*.user
*.suo
*.ipch
*.sdf
*.opensdf
*.DS_Store
/test-driver
*.log
*.trs
/build
/subprojects
include: "https://gitlab.freedesktop.org/gstreamer/gst-ci/raw/master/gitlab/ci_template.yml"
[submodule "common"]
path = common
url = git://anongit.freedesktop.org/gstreamer/common
url = https://gitlab.freedesktop.org/gstreamer/common.git
......@@ -3,7 +3,7 @@ Matt Howell <mhowell@users.sourceforge.net>
Brent Bradburn <bbradburn@users.sourceforge.net>
Wim Taymans <wim.taymans@chello.be>
Richard Boulton <richard@tartarus.org>
Zaheer Merali <zaheer@grid9.net>
Zaheer Abbas Merali <zaheerabbas at merali dot org>
David I. Lehn <dlehn@users.sourceforge.net>
Chris Emerson <chris@tartarus.org>
Jens Thiele <karme@unforgettable.com>
......@@ -18,3 +18,4 @@ Benjamin Otte <in7y118@public.uni-hamburg.de>
Ronald Bultje <rbultje@ronald.bitfreak.net>
Julien MOUTTE <julien@moutte.net>
Jan Schmidt <thaytan@mad.scientist.com>
Arwed v. Merkatz <v.merkatz@gmx.net>
This diff is collapsed.
This diff is collapsed.
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 `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' 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
documentation.
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
this:
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
architecture.
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:
CPU-COMPANY-SYSTEM
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 `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' 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
operates.
`--cache-file=FILE'
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'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
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).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
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 (http://www.xiph.org/paranoia/)
aasink aalib (http://aa-project.sourceforge.net/aalib/)
xmms libxmms (http://www.xmms.org)
decdvd ac3dec,mpeg2dec (http://linuxvideo.org/mpeg2dec/,http://linuxvideo.org/ac3dec/)
sidplay libsidplay (http://www.geocities.com/SiliconValley/Lakes/5147/sidplay/)
Plugins derived from GPL code are as follows:
synaesthesia synaesthesia (http://yoyo.cc.monash.edu.au/~pfh/synaesthesia.html)
Plugins which use a LGPL library are as follows:
Colorspace Hermes (http://www.clanlib.org/hermes/)
httpsrc libghttp (ftp.gnome.org/pub/GNOME/stable/sources/libghttp/)
alsasink alsa (http://alsa-project.org)
aRts aRts (http://arts-project.org)
sdlsink libsdl (http://www.libsdl.org)
gnomevfssource gnome-vfs (ftp.gnome.org//pub/GNOME/stable/sources/gnome-vfs)
gnomevfssink gnome-vfs
esdsink libesd (ftp.gnome.org/pub/GNOME/stable/sources/esound)
icastsend libshout (http://www.icecast.org)
lame libmp3lame (http://www.mp3dev.org/mp3/)
gst1394 libraw1394 (http://linux1394.sourceforge.net)
flac libFLAC (http://flac.sourceforge.net)
RTP ortp (http://www.linphone.org/ortp/)
Effectv effectv (http://effectv.sourceforge.net)
ffmpeg ffmpeg (http://ffmpeg.sourceforge.net)
Plugins which use a BSD covered library are as follows:
vorbisenc libogg/libvorbis (http://www.xiph.org/ogg/vorbis)
vorbisdec libogg/libvorbis
Plugins based on libraries with other free licenses:
xsink libXv (MIT X11 / X Consortium license)
gsm libgsm (MIT license http://kbs.cs.tu-berlin.de/~jutta/toast.html)
Plugins using non-free libraries:
xamp3 decoder libxaudio (http://www.xaudio.com/)
wincodec win32ddl (http://divx.euro.ru/)
GStreamer is currently maintained by the consensus of a number
of people, including, but not limited to:
David Schleef <ds@schleef.org>
Benjamin Otte <in7y118@public.uni-hamburg.de>
Ronald Bultje <rbultje@ronald.bitfreak.net>
Thomas Vander Stichele <thomas@apestaart.org>
Jan Schmidt <thaytan@noraisin.net>
Wim Taymans <wim.taymans@gmail.com>
David Schleef <ds@schleef.org>
Tim-Philipp Müller <tim centricular net>
Sebastian Dröge <slomo@coaxion.net>
Maintainer-related issues should be addressed to:
gstreamer-devel@lists.sourceforge.net
gstreamer-devel@lists.freedesktop.org
if USE_GCONFTOOL
GCONF_DIR=gconf
else
GCONF_DIR=
endif
DISTCHECK_CONFIGURE_FLAGS=--enable-gtk-doc
if BUILD_EXTERNAL
EXT_DIR=ext
else
EXT_DIR=
endif
ALWAYS_SUBDIRS = \
gst sys ext \
tests \
docs \
po \
common \
m4 \
pkgconfig
if BUILD_EXAMPLES
EXAMPLES_DIR=examples
else
EXAMPLES_DIR=
endif
SUBDIRS = $(ALWAYS_SUBDIRS)
SUBDIRS=gst-libs \
gst sys $(EXT_DIR) \
$(EXAMPLES_DIR) \
tools \
$(GCONF_DIR) \
testsuite \
po \
common \
m4 \
pkgconfig
DIST_SUBDIRS = $(ALWAYS_SUBDIRS)
DIST_SUBDIRS=ext gst-libs \
gst sys \
examples \
tools \
gconf \
testsuite \
po \
common \
m4 \
pkgconfig
EXTRA_DIST = \
depcomp \
AUTHORS COPYING NEWS README RELEASE REQUIREMENTS \
ChangeLog gst-plugins-good.doap autogen.sh \
$(shell find "$(top_srcdir)" -type f -name meson.build ! -path "$(top_srcdir)/$(PACKAGE_TARNAME)-*" ) \
meson_options.txt
DISTCLEANFILES = _stdint.h
EXTRA_DIST=gst-plugins.spec depcomp \
AUTHORS COPYING COPYING.LIB NEWS README RELEASE REQUIREMENTS \
ChangeLog autogen.sh
noinst_HEADERS = \
gst-libs/gst/gettext.h \
gst-libs/gst/gst-i18n-plugin.h \
gst-libs/gst/glib-compat-private.h
DISTCLEANFILES=_stdint.h
ACLOCAL_AMFLAGS = -I m4 -I common/m4
include $(top_srcdir)/common/release.mak
include $(top_srcdir)/common/po.mak
check-valgrind:
$(MAKE) -C tests/check check-valgrind
if HAVE_GST_CHECK
check-torture:
$(MAKE) -C tests/check torture
build-checks:
$(MAKE) -C tests/check build-checks
else
check-torture:
true
build-checks:
true
endif
include $(top_srcdir)/common/coverage/lcov.mak
# cruft: plugins that have been merged or moved or renamed
CRUFT_FILES = \
$(top_builddir)/gst-plugins-good.spec \
$(top_builddir)/win32/common/config.h-new \
$(top_builddir)/common/shave \
$(top_builddir)/common/shave-libtool \
$(top_builddir)/docs/plugins/xml/plugin-shout2send.xml \
$(top_builddir)/ext/pulse/.libs/libgstpulse.so \
$(top_builddir)/ext/soup/.libs/libgstsouphttpsrc.so \
$(top_builddir)/gst/median/.libs/*.{so,dll,DLL,dylib} \
$(top_builddir)/gst/qtdemux/.libs/*.{so,dll,DLL,dylib} \
$(top_builddir)/gst/quicktime/.libs/*.{so,dll,DLL,dylib} \
$(top_builddir)/gst/videofilter/.libs/*videoflip.{so,dll,DLL,dylib} \
$(top_builddir)/gst/videofilter/.libs/*videobalance.{so,dll,DLL,dylib} \
$(top_builddir)/gst/videofilter/.libs/*gamma.{so,dll,DLL,dylib} \
$(top_builddir)/sys/directsound/.libs/libgstdirectsoundsink.{dll,DLL} \
$(top_builddir)/sys/oss4/.libs/libgstoss4audio.so \
$(top_builddir)/sys/waveform/.libs/libgstwaveformsink.{dll,DLL}
CRUFT_DIRS = \
$(top_srcdir)/docs/plugins/tmpl \
$(top_srcdir)/gst/median \
$(top_srcdir)/gst/qtdemux \
$(top_srcdir)/gst/quicktime \
$(top_srcdir)/ext/annodex \
$(top_srcdir)/tests/examples/pulse
include $(top_srcdir)/common/cruft.mak
all-local: check-cruft
This diff is collapsed.
This diff is collapsed.
=================================
GStreamer Static Linking README
=================================
DRAFT, April 2013
I. INTRODUCTION
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.
II. DISCLAIMER
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").
III. THE SPIRIT OF THE LGPL LICENSE
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