gstreamer/validate
Thibault Saunier 53628bd7f2 validate:scenario: Factor out code to check position
Summary:
Making simpler to follow the execute_next_action function.

Depends on D169

Reviewers: Mathieu_Du

Differential Revision: http://phabricator.freedesktop.org/D170
2015-05-14 15:56:56 +02:00
..
common@92e7a485ce Update common submodule 2015-04-23 11:24:14 +02:00
data validate: ignore x264 valgrind errors 2015-05-11 21:55:24 +02:00
docs validate: Reshape documentation 2015-05-11 21:56:27 +02:00
gst validate:scenario: Factor out code to check position 2015-05-14 15:56:56 +02:00
launcher validate: disable QOS features when running with valgrind 2015-05-11 21:55:24 +02:00
pkgconfig validate: fix installation 2013-11-25 16:56:11 -03:00
po validate: Update autogen.sh 2015-04-23 11:52:41 +02:00
tests validate: add gst_validate_deinit() 2015-05-11 21:55:24 +02:00
tools validate: add gst_validate_deinit() 2015-05-11 21:55:24 +02:00
.gitignore update gitignore 2015-05-04 14:48:26 +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.4.0 2014-10-20 13:24:29 +02:00
configure.ac validate: Add a gtk plugins that implements action types relative to Gtk 2015-05-14 15:56:56 +02: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 validate: Update autogen.sh 2015-04-23 11:52:41 +02:00
Makefile.am validate: add gstvalidate.supp valgrind suppression file 2015-04-20 15:29:28 +02:00
multi-pre-commit.hook validate: update pre-commit hook. 2014-10-30 15:40:17 +01:00
NEWS Release 1.4.0 2014-10-20 13:24:29 +02:00
pre-commit-python.hook validate: pre commit hook: Do not try to run pep8 on non python files! 2014-11-25 19:41:01 +01:00
README docs: update and improve 2013-09-02 16:09:07 -03: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