mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-18 07:47:17 +00:00
building up speed
Original commit message from CVS: building up speed
This commit is contained in:
Thomas Vander Stichele
commit
754313ab71
5 changed files with 1631 additions and 0 deletions
182
INSTALL
Normal file
182
INSTALL
Normal file
|
|
@ -0,0 +1,182 @@
|
||||||
|
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.
|
||||||
3
Makefile.am
Normal file
3
Makefile.am
Normal file
|
|
@ -0,0 +1,3 @@
|
||||||
|
SUBDIRS=sys
|
||||||
|
|
||||||
|
DIST_SUBDIRS=sys
|
||||||
60
acconfig.h
Normal file
60
acconfig.h
Normal file
|
|
@ -0,0 +1,60 @@
|
||||||
|
#undef PACKAGE
|
||||||
|
#undef VERSION
|
||||||
|
#undef GST_VERSION_RELEASE
|
||||||
|
|
||||||
|
/* Gettext stuff */
|
||||||
|
#undef ENABLE_NLS
|
||||||
|
#undef HAVE_CATGETS
|
||||||
|
#undef HAVE_GETTEXT
|
||||||
|
#undef HAVE_LC_MESSAGES
|
||||||
|
#undef HAVE_STPCPY
|
||||||
|
|
||||||
|
#undef USE_GLIB2
|
||||||
|
#undef HAVE_LIBXML2
|
||||||
|
|
||||||
|
#undef PLUGINS_DIR
|
||||||
|
#undef PLUGINS_BUILDDIR
|
||||||
|
#undef PLUGINS_USE_BUILDDIR
|
||||||
|
|
||||||
|
#undef GST_CONFIG_DIR
|
||||||
|
#undef GST_WIN32_LIBDIR
|
||||||
|
|
||||||
|
#undef HAVE_CPU_I386
|
||||||
|
#undef HAVE_CPU_PPC
|
||||||
|
#undef HAVE_CPU_ALPHA
|
||||||
|
#undef HAVE_CPU_ARM
|
||||||
|
#undef HAVE_CPU_SPARC
|
||||||
|
|
||||||
|
#undef HAVE_RDTSC
|
||||||
|
|
||||||
|
#undef HAVE_LIBGHTTP
|
||||||
|
#undef HAVE_LIBMMX
|
||||||
|
#undef HAVE_LIBXV
|
||||||
|
#undef HAVE_OSS
|
||||||
|
#undef HAVE_XAUDIO
|
||||||
|
#undef HAVE_LIBDVDREAD
|
||||||
|
#undef HAVE_VORBIS
|
||||||
|
#undef HAVE_AALIB
|
||||||
|
#undef HAVE_LIBMAD
|
||||||
|
#undef HAVE_LIBMIKMOD
|
||||||
|
#undef HAVE_LIBJPEG
|
||||||
|
#undef HAVE_LIBGSM
|
||||||
|
#undef HAVE_LIBSDL
|
||||||
|
#undef HAVE_LIBHERMES
|
||||||
|
#undef HAVE_NASM
|
||||||
|
#undef HAVE_A52DEC
|
||||||
|
#undef HAVE_MPEG2DEC
|
||||||
|
#undef HAVE_FLACLIB
|
||||||
|
#undef HAVE_LIBRTP
|
||||||
|
#undef HAVE_LINUX_CDROM
|
||||||
|
#undef HAVE_LINUX_VIDEODEV
|
||||||
|
#undef HAVE_LIBSDL
|
||||||
|
#undef HAVE_LIBOPENQUICKTIME
|
||||||
|
|
||||||
|
#undef HAVE_ATOMIC_H
|
||||||
|
|
||||||
|
#undef GST_DEBUG_ENABLED
|
||||||
|
#undef GST_INFO_ENABLED
|
||||||
|
#undef GST_DEBUG_COLOR
|
||||||
|
|
||||||
|
#undef GST_DISABLE_LOADSAVE
|
||||||
167
autogen.sh
Executable file
167
autogen.sh
Executable file
|
|
@ -0,0 +1,167 @@
|
||||||
|
#!/bin/bash
|
||||||
|
# Run this to generate all the initial makefiles, etc.
|
||||||
|
|
||||||
|
DIE=0
|
||||||
|
package=gstreamer-plugins
|
||||||
|
srcfile=own/sinesrc/gstsinesrc.c
|
||||||
|
#DEBUG=defined
|
||||||
|
if test "x$1" = "x-d"; then echo "+ debug output enabled"; DEBUG=defined; fi
|
||||||
|
|
||||||
|
debug ()
|
||||||
|
# print out a debug message if DEBUG is a defined variable
|
||||||
|
{
|
||||||
|
if test ! -z "$DEBUG"
|
||||||
|
then
|
||||||
|
echo "DEBUG: $1"
|
||||||
|
fi
|
||||||
|
}
|
||||||
|
|
||||||
|
version_check ()
|
||||||
|
# check the version of a package
|
||||||
|
# first argument : package name (executable)
|
||||||
|
# second argument : source download url
|
||||||
|
# rest of arguments : major, minor, micro version
|
||||||
|
{
|
||||||
|
PACKAGE=$1
|
||||||
|
URL=$2
|
||||||
|
MAJOR=$3
|
||||||
|
MINOR=$4
|
||||||
|
MICRO=$5
|
||||||
|
|
||||||
|
WRONG=
|
||||||
|
|
||||||
|
debug "major $MAJOR minor $MINOR micro $MICRO"
|
||||||
|
VERSION=$MAJOR
|
||||||
|
if test ! -z "$MINOR"; then VERSION=$VERSION.$MINOR; else MINOR=0; fi
|
||||||
|
if test ! -z "$MICRO"; then VERSION=$VERSION.$MICRO; else MICRO=0; fi
|
||||||
|
|
||||||
|
debug "major $MAJOR minor $MINOR micro $MICRO"
|
||||||
|
echo -n "+ checking for $1 >= $VERSION ... "
|
||||||
|
($PACKAGE --version) < /dev/null > /dev/null 2>&1 ||
|
||||||
|
{
|
||||||
|
echo
|
||||||
|
echo "You must have $PACKAGE installed to compile $package."
|
||||||
|
echo "Download the appropriate package for your distribution,"
|
||||||
|
echo "or get the source tarball at $URL"
|
||||||
|
return 1
|
||||||
|
}
|
||||||
|
# the following line is carefully crafted sed magic
|
||||||
|
pkg_version=`$PACKAGE --version|head -n 1|sed 's/^[a-zA-z\.\ ()]*//;s/ .*$//'`
|
||||||
|
debug "pkg_version $pkg_version"
|
||||||
|
pkg_major=`echo $pkg_version | cut -d. -f1`
|
||||||
|
pkg_minor=`echo $pkg_version | cut -d. -f2`
|
||||||
|
pkg_micro=`echo $pkg_version | cut -d. -f3`
|
||||||
|
test -z "$pkg_minor" && pkg_minor=0
|
||||||
|
test -z "$pkg_micro" && pkg_micro=0
|
||||||
|
|
||||||
|
debug "found major $pkg_major minor $pkg_minor micro $pkg_micro"
|
||||||
|
|
||||||
|
#start checking the version
|
||||||
|
debug "version check"
|
||||||
|
|
||||||
|
if [ ! "$pkg_major" \> "$MAJOR" ]; then
|
||||||
|
debug "$pkg_major <= $MAJOR"
|
||||||
|
if [ "$pkg_major" \< "$MAJOR" ]; then
|
||||||
|
WRONG=1
|
||||||
|
elif [ ! "$pkg_minor" \> "$MINOR" ]; then
|
||||||
|
if [ "$pkg_minor" \< "$MINOR" ]; then
|
||||||
|
WRONG=1
|
||||||
|
elif [ "$pkg_micro" \< "$MICRO" ]; then
|
||||||
|
WRONG=1
|
||||||
|
fi
|
||||||
|
fi
|
||||||
|
fi
|
||||||
|
|
||||||
|
if test ! -z "$WRONG"; then
|
||||||
|
echo "found $pkg_version, not ok !"
|
||||||
|
echo
|
||||||
|
echo "You must have $PACKAGE $VERSION or greater to compile $package."
|
||||||
|
echo "Get the latest version from $URL"
|
||||||
|
return 1
|
||||||
|
else
|
||||||
|
echo "found $pkg_version, ok."
|
||||||
|
fi
|
||||||
|
}
|
||||||
|
|
||||||
|
# autoconf 2.52d has a weird issue involving a yes:no error
|
||||||
|
# so don't allow it's use
|
||||||
|
ac_version=`autoconf --version|head -n 1|sed 's/^[a-zA-z\.\ ()]*//;s/ .*$//'`
|
||||||
|
if test "$ac_version" = "2.52d"; then
|
||||||
|
echo "autoconf 2.52d has an issue with our current build."
|
||||||
|
echo "We don't know who's to blame however. So until we do, get a"
|
||||||
|
echo "regular version. RPM's of a working version are on the gstreamer site."
|
||||||
|
exit 1
|
||||||
|
fi
|
||||||
|
|
||||||
|
|
||||||
|
version_check "autoconf" "ftp://ftp.gnu.org/pub/gnu/autoconf/" 2 52 || DIE=1
|
||||||
|
version_check "automake" "ftp://ftp.gnu.org/pub/gnu/automake/" 1 5 || DIE=1
|
||||||
|
version_check "libtool" "ftp://ftp.gnu.org/pub/gnu/libtool/" 1 4 0 || DIE=1
|
||||||
|
version_check "pkg-config" "http://www.freedesktop.org/software/pkgconfig" 0 8 0 || DIE=1
|
||||||
|
|
||||||
|
if test "$DIE" -eq 1; then
|
||||||
|
exit 1
|
||||||
|
fi
|
||||||
|
|
||||||
|
test -f $srcfile || {
|
||||||
|
echo "You must run this script in the top-level $package directory"
|
||||||
|
exit 1
|
||||||
|
}
|
||||||
|
|
||||||
|
if test -z "$*"; then
|
||||||
|
echo "I am going to run ./configure with no arguments - if you wish "
|
||||||
|
echo "to pass any to it, please specify them on the $0 command line."
|
||||||
|
fi
|
||||||
|
|
||||||
|
echo "+ creating acinclude.m4"
|
||||||
|
cat m4/*.m4 > acinclude.m4
|
||||||
|
|
||||||
|
echo "+ running aclocal ..."
|
||||||
|
aclocal $ACLOCAL_FLAGS || {
|
||||||
|
echo
|
||||||
|
echo "aclocal failed - check that all needed development files are present on system"
|
||||||
|
exit 1
|
||||||
|
}
|
||||||
|
|
||||||
|
# FIXME : why does libtoolize keep complaining about aclocal ?
|
||||||
|
echo "+ running libtoolize ..."
|
||||||
|
libtoolize --copy --force
|
||||||
|
|
||||||
|
echo "+ running autoheader ... "
|
||||||
|
autoheader || {
|
||||||
|
echo
|
||||||
|
echo "autoheader failed"
|
||||||
|
exit 1
|
||||||
|
}
|
||||||
|
echo "+ running autoconf ... "
|
||||||
|
autoconf || {
|
||||||
|
echo
|
||||||
|
echo "autoconf failed"
|
||||||
|
exit 1
|
||||||
|
}
|
||||||
|
echo "+ running automake ... "
|
||||||
|
automake -a -c || {
|
||||||
|
echo
|
||||||
|
echo "automake failed"
|
||||||
|
exit 1
|
||||||
|
}
|
||||||
|
|
||||||
|
# now remove the cache, because it can be considered dangerous in this case
|
||||||
|
#echo "+ removing config.cache ... "
|
||||||
|
#rm -f config.cache
|
||||||
|
|
||||||
|
CONFIGURE_OPT='--enable-maintainer-mode --enable-plugin-builddir --enable-debug --enable-DEBUG'
|
||||||
|
|
||||||
|
echo "+ running configure ... "
|
||||||
|
echo "./configure default flags: $CONFIGURE_OPT"
|
||||||
|
echo "using: $CONFIGURE_OPT $@"
|
||||||
|
echo
|
||||||
|
|
||||||
|
./configure $CONFIGURE_OPT "$@" || {
|
||||||
|
echo
|
||||||
|
echo "configure failed"
|
||||||
|
exit 1
|
||||||
|
}
|
||||||
|
|
||||||
|
echo
|
||||||
|
echo "Now type 'make' to compile $package."
|
||||||
1219
configure.ac
Normal file
1219
configure.ac
Normal file
File diff suppressed because it is too large
Load diff
Loading…
Reference in a new issue