gstreamer/validate
2019-06-26 12:09:03 -04:00
..
common@59cb678164 Automatic update of common submodule 2018-12-06 11:53:33 +02:00
data validate:scenario: Implement a way to execute an action on message 2019-04-03 13:38:42 +00:00
docs doc: Port to hotdoc 2019-05-13 11:37:38 -04:00
gst validate: Add SCENARIO_NAME and CONFIG_NAME vars in configs/scenarios 2019-06-26 12:09:03 -04:00
gst-libs validate: Update for g_type_class_add_private() deprecation in recent GLib 2018-09-20 15:16:16 -03:00
launcher validate: Set 'LOGSDIR' variable in scenarios and config files 2019-06-23 03:10:34 -04:00
pkgconfig validate: pkgconfig: fix libtool-ism in uninstalled .pc file 2017-02-15 18:13:14 +00:00
plugins ssim: Report critical issue when override not attached 2019-05-23 11:52:00 -04:00
po validate: Update autogen.sh 2015-04-23 11:52:41 +02:00
tests meson: Use dep.type_name() when it makes sense 2019-05-13 11:37:38 -04:00
tools validate: Misc leaks plugging 2019-06-18 18:13:03 -04:00
win32 validate: win32: add new api to export file 2019-04-11 01:02:14 +01:00
.gitignore validate: Update all gitignore 2018-06-05 16:25:46 +02:00
AUTHORS qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
autogen.sh validate: Always git submodule update from the toplevel directory 2015-05-12 09:55:58 +02:00
ChangeLog Release 1.16.0 2019-04-19 00:36:54 +01:00
configure.ac doc: Port to hotdoc 2019-05-13 11:37:38 -04: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
Makefile.am doc: Port to hotdoc 2019-05-13 11:37:38 -04:00
meson.build doc: Port to hotdoc 2019-05-13 11:37:38 -04:00
NEWS Release 1.16.0 2019-04-19 00:36:54 +01:00
README docs: update and improve 2013-09-02 16:09:07 -03: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

The 'master' branch uses gstreamer 1.0, there is a '0.10' branch for
gstreamer 0.10. The default is the 'master' branch, if you want to use it
for 0.10, do:

git checkout --track origin/0.10

Build with:

./autogen.sh --prefix=<installation-prefix>
make
sudo make 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