mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-14 05:12:09 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/tools/Makefile.am

49 lines
1.3 KiB
Makefile
Raw Permalink Normal View History

Lots of modifications to the plugin system. Original commit message from CVS: Lots of modifications to the plugin system. - Added a GstPluginfeature object that serves as a base class for all plugin contents. - changed the plugin API, everyhting is now added with gst_plugin_add_feature - typefactories are named now so that they can be located easily and filled in at plugin load. - mime types like "video/raw image/raw" are gone for now. - lots of plugin updates (style and API changes) - tested with an without registry. - updates to various tools. - added a little testsuite to test/show how you can load plugins (4 modes) Test this one, Almost everything has changed :-)
2001-08-21 20:16:48 +00:00
tools: remove unversioned gst-launch, gst-inspect and gst-typefind The unversioned tool wrappers are confusing and annoying for packagers, users and developers alike. A gst-launch pipeline that works in 0.10 will likely not work in 0.11 (e.g. because elements or properties get renamed, or syntax changes). The unversioned tools also yield useless results when used with gdb or valgrind. Packagers need to co-ordinate the packaging of all major versions to make sure there are no conflicts when both try to install the same files. When two major versions are in use (e.g. 0.10 and 0.11/1.0), it may be unclear (when looking at things on IRC/pastebin/mailing list etc.) which version is actually being used when there are unversioned wrappers. For all these reasons, it seems best to just remove them for now.
2011-06-05 13:10:50 +00:00
bin_PROGRAMS = \
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst-inspect-@GST_API_VERSION@ \
stats: add a stats frontend Parse the log and collect data from tracer messages.
2013-11-04 19:11:09 +00:00
gst-stats-@GST_API_VERSION@ \
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst-typefind-@GST_API_VERSION@
add gst-run wrapper code build original tools as versioned tools Original commit message from CVS: add gst-run wrapper code build original tools as versioned tools
2004-02-04 18:02:55 +00:00
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst_inspect_@GST_API_VERSION@_SOURCES = gst-inspect.c tools.h
gst_inspect_@GST_API_VERSION@_CFLAGS = $(GST_OBJ_CFLAGS)
gst_inspect_@GST_API_VERSION@_LDADD = $(GST_OBJ_LIBS)
tools: remove unversioned gst-launch, gst-inspect and gst-typefind The unversioned tool wrappers are confusing and annoying for packagers, users and developers alike. A gst-launch pipeline that works in 0.10 will likely not work in 0.11 (e.g. because elements or properties get renamed, or syntax changes). The unversioned tools also yield useless results when used with gdb or valgrind. Packagers need to co-ordinate the packaging of all major versions to make sure there are no conflicts when both try to install the same files. When two major versions are in use (e.g. 0.10 and 0.11/1.0), it may be unclear (when looking at things on IRC/pastebin/mailing list etc.) which version is actually being used when there are unversioned wrappers. For all these reasons, it seems best to just remove them for now.
2011-06-05 13:10:50 +00:00
stats: add a stats frontend Parse the log and collect data from tracer messages.
2013-11-04 19:11:09 +00:00
gst_stats_@GST_API_VERSION@_SOURCES = gst-stats.c tools.h
gst_stats_@GST_API_VERSION@_CFLAGS = $(GST_OBJ_CFLAGS)
gst_stats_@GST_API_VERSION@_LDADD = $(GST_OBJ_LIBS)
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst_typefind_@GST_API_VERSION@_SOURCES = gst-typefind.c tools.h
gst_typefind_@GST_API_VERSION@_CFLAGS = $(GST_OBJ_CFLAGS)
gst_typefind_@GST_API_VERSION@_LDADD = $(GST_OBJ_LIBS)
add gst-run wrapper code build original tools as versioned tools Original commit message from CVS: add gst-run wrapper code build original tools as versioned tools
2004-02-04 18:02:55 +00:00
various fixes to make Original commit message from CVS: * configure.ac: * gst/Makefile.am: * gst/gst.c: * gst/gstplugin.h: * gst/gstregistry.h: * tests/benchmarks/complexity.c: * tests/benchmarks/mass-elements.c: * tests/check/Makefile.am: * tools/Makefile.am: * tools/gst-inspect.c: * tools/gst-xmlinspect.c: various fixes to make --disable-nls --disable-registry --disable-loadsave --disable-parse --disable-gst-debug work and get the core .so down to 360444 bytes after stripping
2005-11-30 19:01:53 +00:00
if !GST_DISABLE_PARSE
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
bin_PROGRAMS += gst-launch-@GST_API_VERSION@
add gst-run wrapper code build original tools as versioned tools Original commit message from CVS: add gst-run wrapper code build original tools as versioned tools
2004-02-04 18:02:55 +00:00
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst_launch_@GST_API_VERSION@_SOURCES = gst-launch.c tools.h
gst_launch_@GST_API_VERSION@_CFLAGS = $(GST_OBJ_CFLAGS)
gst_launch_@GST_API_VERSION@_LDADD = $(GST_OBJ_LIBS)
tools: remove unversioned gst-launch, gst-inspect and gst-typefind The unversioned tool wrappers are confusing and annoying for packagers, users and developers alike. A gst-launch pipeline that works in 0.10 will likely not work in 0.11 (e.g. because elements or properties get renamed, or syntax changes). The unversioned tools also yield useless results when used with gdb or valgrind. Packagers need to co-ordinate the packaging of all major versions to make sure there are no conflicts when both try to install the same files. When two major versions are in use (e.g. 0.10 and 0.11/1.0), it may be unclear (when looking at things on IRC/pastebin/mailing list etc.) which version is actually being used when there are unversioned wrappers. For all these reasons, it seems best to just remove them for now.
2011-06-05 13:10:50 +00:00
endif
trim fat from nonversioned binaries Original commit message from CVS: trim fat from nonversioned binaries
2004-03-02 10:38:40 +00:00
tools: remove unversioned gst-launch, gst-inspect and gst-typefind The unversioned tool wrappers are confusing and annoying for packagers, users and developers alike. A gst-launch pipeline that works in 0.10 will likely not work in 0.11 (e.g. because elements or properties get renamed, or syntax changes). The unversioned tools also yield useless results when used with gdb or valgrind. Packagers need to co-ordinate the packaging of all major versions to make sure there are no conflicts when both try to install the same files. When two major versions are in use (e.g. 0.10 and 0.11/1.0), it may be unclear (when looking at things on IRC/pastebin/mailing list etc.) which version is actually being used when there are unversioned wrappers. For all these reasons, it seems best to just remove them for now.
2011-06-05 13:10:50 +00:00
manpages = \
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst-inspect-@GST_API_VERSION@.1 \
tools: dist new gst-stats man page Fixes meson build from tarball.
2017-05-20 15:44:14 +00:00
gst-stats-@GST_API_VERSION@.1 \
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
gst-typefind-@GST_API_VERSION@.1
install docs versioned Original commit message from CVS: install docs versioned
2004-02-04 18:27:39 +00:00
tools: remove unversioned gst-launch, gst-inspect and gst-typefind The unversioned tool wrappers are confusing and annoying for packagers, users and developers alike. A gst-launch pipeline that works in 0.10 will likely not work in 0.11 (e.g. because elements or properties get renamed, or syntax changes). The unversioned tools also yield useless results when used with gdb or valgrind. Packagers need to co-ordinate the packaging of all major versions to make sure there are no conflicts when both try to install the same files. When two major versions are in use (e.g. 0.10 and 0.11/1.0), it may be unclear (when looking at things on IRC/pastebin/mailing list etc.) which version is actually being used when there are unversioned wrappers. For all these reasons, it seems best to just remove them for now.
2011-06-05 13:10:50 +00:00
if !GST_DISABLE_PARSE
gst: Change versioning Remove GST_MAJORMINOR and replace it by GST_API_VERSION Also set GST_VERSION_{MAJOR,MINOR,MICRO,NANO} explicitely now. All versions are at 1.0.0 now for the release soon but API/ABI can still change until the 1.0.0 release. Next release versions until 1.0.0 will be 0.10.9X and these will be release candidates. GST_VERSION_* will nonetheless stay at 1.0.0.0.
2012-04-04 11:13:52 +00:00
manpages += gst-launch-@GST_API_VERSION@.1
tools: remove unversioned gst-launch, gst-inspect and gst-typefind The unversioned tool wrappers are confusing and annoying for packagers, users and developers alike. A gst-launch pipeline that works in 0.10 will likely not work in 0.11 (e.g. because elements or properties get renamed, or syntax changes). The unversioned tools also yield useless results when used with gdb or valgrind. Packagers need to co-ordinate the packaging of all major versions to make sure there are no conflicts when both try to install the same files. When two major versions are in use (e.g. 0.10 and 0.11/1.0), it may be unclear (when looking at things on IRC/pastebin/mailing list etc.) which version is actually being used when there are unversioned wrappers. For all these reasons, it seems best to just remove them for now.
2011-06-05 13:10:50 +00:00
endif
install docs versioned Original commit message from CVS: install docs versioned
2004-02-04 18:27:39 +00:00
man_MANS = $(manpages)
distcheck fixes Original commit message from CVS: distcheck fixes
2004-03-15 18:20:03 +00:00
# developer helper tools, not meant for installation
noinst_SCRIPTS = gst-indent
tools/: Add back --version command line option (#340460). Original commit message from CVS: * tools/Makefile.am: * tools/gst-inspect.c: (main): * tools/gst-launch.c: (main): * tools/gst-xmlinspect.c: (main): * tools/tools.h: Add back --version command line option (#340460). * tools/gst-typefind.c: (have_type_handler), (typefind_file), (main): Add --version option and use GOption for argument parsing; refactor a bit; accept directories as arguments and recurse into them; lastly, print a decent error message when things go wrong.
2006-05-05 17:07:42 +00:00
noinst_HEADERS = tools.h
install docs versioned Original commit message from CVS: install docs versioned
2004-02-04 18:27:39 +00:00
EXTRA_DIST = \
tools: fix distcheck and .gitignore
2016-11-23 09:58:44 +00:00
gst-inspect-@GST_API_VERSION@.1 \
gst-typefind-@GST_API_VERSION@.1 \
gst-launch-@GST_API_VERSION@.1 \
tools: dist new gst-stats man page Fixes meson build from tarball.
2017-05-20 15:44:14 +00:00
gst-stats-@GST_API_VERSION@.1 \
tools: ship the final man pages directly, no more man pages templates Don't use templates for the man pages, the API version change is a rare event, so it's not really worth keeping in place the "sed" boilerplate to have it set at build time. Shipping the final man pages directly also makes it easer to install the man pages with meson (in a future commit). Note that now all the occurrences of the programs names have the API version as a suffix. Traditionally the example command lines looked like: gst-launch ... Now they look like: gst-launch-1.0 ... This reflects the actual programs names and makes it easier to copy and paste the example commands. Also, the .gitignore file is adjusted not to ignore the final man pages anymore. You may need to clean your src/build directory before pulling in this patch. https://bugzilla.gnome.org/show_bug.cgi?id=773917
2016-11-03 09:30:53 +00:00
$(noinst_SCRIPTS)
Reference in a new issue Copy permalink