gstreamer/validate
2016-11-23 08:38:49 -03:00
..
common@eb6a86e9e6 Update common submodule 2015-08-21 11:09:48 +02:00
data scenarios: Simplify Makefile 2016-10-26 17:58:58 +02:00
docs meson: Fix gtkdoc using new meson features 2016-09-28 20:36:46 -03:00
gst validate: Fix GI warnings 2016-11-23 08:38:49 -03:00
gst-libs validate: inherit from GstObject instead of GObject 2016-08-01 10:45:37 -04:00
launcher validate: Minor documentation fixes. 2016-11-17 15:43:15 -03:00
pkgconfig validate: Add support for Meson as alternative/parallel build system 2016-08-25 15:12:31 -03:00
plugins validate: Add support for Meson as alternative/parallel build system 2016-08-25 15:12:31 -03:00
po validate: Update autogen.sh 2015-04-23 11:52:41 +02:00
tests Revert "meson: move gstreamer-check-1.0 dependency to validate/tests/check" 2016-10-25 11:48:12 +05:30
tools Fix MSVC const warnings 2016-11-17 17:36:03 -03:00
win32 validate: make: include common/win32.mak 2016-11-19 11:54:06 +02:00
.gitignore validate: Add support for Meson as alternative/parallel build system 2016-08-25 15:12:31 -03: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.10.0 2016-11-01 18:16:13 +02:00
configure.ac validate: Use gst_debug_get_stack_trace instead of our implementation 2016-11-09 10:55:40 -03: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.10.0 2016-11-01 18:16:13 +02:00
Makefile.am validate: make: include common/win32.mak 2016-11-19 11:54:06 +02:00
meson.build meson: Move vs_module_defs_dir to the validate subdirectory 2016-11-19 12:36:32 +02:00
NEWS Release 1.10.0 2016-11-01 18:16:13 +02: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