gstreamer/validate/launcher/apps/Makefile.am

appsdir = $(libdir)/gst-validate-launcher/python/launcher/apps/

SUBDIRS =

apps_PYTHON = \
	__init__.py \
	gstvalidate.py \
	pyunittest.py \
	gstcheck.py
validate:tools: Do not forget to add Makefile.am and main.py 2014-01-09 17:43:15 +00:00			`appsdir = $(libdir)/gst-validate-launcher/python/launcher/apps/`

validate: Remove the default testsuite implementation The default testsuite implementation should belong to the default asset repo where we have the corresponding knowledge. We should style manage a sensible list of known blacklisted tests, encoding profiles, and generators in GstValidate itself and allow testsuite actual implementations to easily use them though the register_default_* methods. This allow us to be able to remove the ugly execfile() call. 2014-11-28 21:42:47 +00:00			`SUBDIRS =`
validate:launcher: Properly handle libsdir when gst-validate is installed + Fix the _in_devel function + Install the validate default testsuite implementation in the right place 2014-08-11 18:19:02 +00:00
validate:tools: Do not forget to add Makefile.am and main.py 2014-01-09 17:43:15 +00:00			`apps_PYTHON = \`
validate:launcher: Do not forget to install apps/__init__.py It is a python module that should be usable by external apps/testsuites 2015-03-06 08:39:10 +00:00			`__init__.py \`
validate: Fix gstcheck when not running on a meson build dir 2017-01-03 16:11:42 +00:00			`gstvalidate.py \`
validate:launcher: Add a TestManager to run python tests Add a stupid simple testsuite made to be configured from the outside 2018-06-15 20:42:32 +00:00			`pyunittest.py \`
validate: Fix gstcheck when not running on a meson build dir 2017-01-03 16:11:42 +00:00			`gstcheck.py`