gstreamer/validate
2020-03-06 15:36:10 -03:00
..
data validate: remove autotools build 2019-10-15 00:24:00 +01:00
docs validate: remove autotools build 2019-10-15 00:24:00 +01:00
gst meson: remove vs_module_defs 2020-02-26 14:21:52 -03:00
gst-libs validate: Add a flags to issues 2020-02-25 11:28:35 -03:00
launcher validate:launcher: Fix printed test number 2020-03-06 15:36:10 -03:00
pkgconfig validate: remove autotools build 2019-10-15 00:24:00 +01:00
plugins validate: Don't use sprintf + glib format modifiers 2020-02-27 19:32:21 +05:30
tests validate: Fix memory leaks 2019-11-20 10:19:00 +01:00
tools validate: remove autotools build 2019-10-15 00:24:00 +01:00
.gitignore validate: remove autotools build 2019-10-15 00:24:00 +01:00
AUTHORS qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
ChangeLog Release 1.16.0 2019-04-19 00:36:54 +01:00
COPYING qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
gst-validate.doap Release 1.16.0 2019-04-19 00:36:54 +01:00
meson.build meson: remove vs_module_defs 2020-02-26 14:21:52 -03:00
NEWS Release 1.16.0 2019-04-19 00:36:54 +01:00
README validate: remove autotools build 2019-10-15 00:24:00 +01:00
RELEASE Back to development 2019-04-19 10:42:30 +01:00

== Gst-Validate

The goal of GstValidate is to be able to detect when elements are not
behaving as expected and report it to the user so he knows how things
are supposed to work inside a GstPipeline. In the end, fixing issues
found by the tool will ensure that all elements behave all together in
the expected way.

The easiest way of using GstValidate is to use one of its command-line
tools, located at tools/ directory. It is also possible to monitor
GstPipelines from any application by using the LD_PRELOAD gstvalidate
lib. The third way of using it is to write your own application that
links and uses libgstvalidate.

== BUILDING

Getting the code:

Releases are available at <URL>, download and extract the tarball. If you
want to use latest git version, do:

git clone <URI>

After cloning or extracting from a tarball, enter the gst-validate directory:

cd gst-validate

Build with:

meson build --prefix=<installation-prefix>
ninja -C build
sudo ninja -C build install (only if you want to install it)

Replace <installation-prefix> with your desired installation path, you can omit
the --prefix argument if you aren't going to install it or if you want the
default /usr/local. It is possible to use gst-validate CLI tools without
installation.

== INSTRUCTIONS

If you are looking for informations on how to use gst-validate -> docs/validate-usage.txt
If you are looking for informations on gst-validate design -> docs/validate-design.txt