%version-entities; ]> Building GStreamer and GStreamer Applications 3 GStreamer Core Building GStreamer and GStreamer Applications How to build the GStreamer framework and applications using it. On UNIX, GStreamer uses the standard GNU build system, using autoconf for package configuration and resolving portability issues, automake for building makefiles that comply with the GNU Coding Standards, and libtool for building shared libraries on multiple platforms. The normal sequence for compiling and installing the GStreamer library is thus: ./configure make make install The standard options provided by GNU autoconf may be passed to the configure script. Please see the autoconf documentation or run ./configure --help for information about the standard options. In addition there are several option to activate or deactivate features. E.g. passing --disable-gst-debug to configure will turn the debugging subsystem into non-functional stub and remove all macro based invokations from within the library (and anything compiled against the library afterwards) If library size matters and one builds in a controlled environment, its also possible to totaly remove sybsystem code. This is intetionally not offered as a configure option as it causes an ABI break. Code build against a version of GStreamer without these modifications needs to be recompiled. make CFLAGS="-DGST_REMOVE_DEPRECATED -DGST_REMOVE_DISABLED" GST_REMOVE_DEPRECATED - Omit deprecated functions from the library. GST_REMOVE_DISABLED - Omit stubs for disabled subsytems from the library. Applications and libraries can use pkg-config to get all the needed compiler and linker flags building against GStreamer. Please note that GStreamer is split into several libraries itself. pkg-config --list-all | grep gstreamer will list the available libraries.