gstreamer

mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-20 08:41:07 +00:00

History

Xavier Claessens cd78cbac86 Fix API visibility macros This copies the logic from GLib discussed there: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2936 Beside being simpler, it also fix all public symbols being annotated with dllexport when doing a static build, as discovered there: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3540#note_1678335 Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3567>		2022-12-20 14:03:35 +00:00
..
data	devenv: Add some missing GStreamer specific env variables	2022-02-25 20:35:26 +00:00
docs	Move files from gst-devtools into the "subprojects/gst-devtools/" subdir	2021-09-24 16:15:38 -03:00
gst	validate: cleanup the use of GST_VALIDATE_API on Windows	2022-11-18 02:17:27 +00:00
gst-libs	validate:ssim: Show original/nok/diff images on error images	2022-10-05 20:29:22 +00:00
launcher	validate:launcher: Cleanup test uuid when copying it	2022-10-05 20:29:22 +00:00
plugins	validate: plug some leaks	2022-11-04 17:59:21 +00:00
tests	video: Fix order of new video formats	2021-10-31 06:38:36 +00:00
tools	validate: Don't deinit too early	2022-11-12 12:24:21 +01:00
.gitignore	Move files from gst-devtools into the "subprojects/gst-devtools/" subdir	2021-09-24 16:15:38 -03:00
COPYING	Move files from gst-devtools into the "subprojects/gst-devtools/" subdir	2021-09-24 16:15:38 -03:00
meson.build	Fix API visibility macros	2022-12-20 14:03:35 +00:00
README	Move files from gst-devtools into the "subprojects/gst-devtools/" subdir	2021-09-24 16:15:38 -03:00

README

== 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