mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-27 20:21:24 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/testsuite/Makefile.am

31 lines
585 B
Makefile
Raw Normal View History

Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
include Rules
added tests for parsing stuff Original commit message from CVS: added tests for parsing stuff
2003-04-10 01:51:42 +00:00
if GST_DISABLE_PARSE
GST_PARSE_DIRS =
else
GST_PARSE_DIRS = parse
endif
GST_DEBUG reorganization containing loads of stuff: Original commit message from CVS: GST_DEBUG reorganization This is a big diff (ca 450k), containing loads of stuff: - gstinfo.[ch] complete rewrite - changing of all GST_DEBUG messages to reflect that change - reorganization of subsystem disabling - addition of gstconfig.h.in so we can track the disablings - <gst/gst.h> does not include <unistd.h> and <config.h> anymore - documentation updated for gstinfo stuff (build the docs yourself to know what changed) - bugfixes for making of the docs (files from CVS are not deleted anymore - testsuite for debugging changes in testsuite/debug expect breakage
2003-06-29 14:05:49 +00:00
if GST_DISABLE_GST_DEBUG
GST_DEBUG_DIRS =
else
GST_DEBUG_DIRS = debug
endif
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
SUBDIRS = bytestream cleanup dynparams \
merge in tagging Original commit message from CVS: merge in tagging Includes: - gsttag.[ch] - The definition of GstTagList and tag registering/querying - gsttaginterface.[ch] - Interface for elements that can handle setting of tags - updates and merges to gststructure.[ch] and gstvalue.[ch] - testsuite/tags - some tests for tagging - bugfixes - updates to make make distcheck work - updates the version number to 0.7.2.1 Does not include: - including tagging stuff in docs - extensive tests
2003-11-24 02:09:23 +00:00
caps plugin elements clock refcounting tags threads \
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
indexers debug $(GST_PARSE_DIRS) $(GST_DEBUG_DIRS)
Added a testsuite. This currently only has one test, which replicates a problem just submitted to the list. Original commit message from CVS: Added a testsuite. This currently only has one test, which replicates a problem just submitted to the list. I hope noone disagrees that we need a testsuite. Also, hopefully we all think that a tiny testsuite which is easy to add tests to is much better than a huge project to create a complete testsuite, which never gets started because its too big and scary. I suggest that tests get created whenever someone has a spare moment, or whenever a bug is reported (to replicate the problem, and thus be sure that when fixed it stays fixed), and before making a change to a piece of code to ensure that it remains working. If we all add little tests occasionally, then we'll have a good useful testsuite before we know it. All you need to do is make a
2001-03-09 12:08:38 +00:00
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
DIST_SUBDIRS = bytestream caps cleanup clock dynparams elements indexers \
merge in tagging Original commit message from CVS: merge in tagging Includes: - gsttag.[ch] - The definition of GstTagList and tag registering/querying - gsttaginterface.[ch] - Interface for elements that can handle setting of tags - updates and merges to gststructure.[ch] and gstvalue.[ch] - testsuite/tags - some tests for tagging - bugfixes - updates to make make distcheck work - updates the version number to 0.7.2.1 Does not include: - including tagging stuff in docs - extensive tests
2003-11-24 02:09:23 +00:00
plugin refcounting tags threads parse debug
Added a testsuite. This currently only has one test, which replicates a problem just submitted to the list. Original commit message from CVS: Added a testsuite. This currently only has one test, which replicates a problem just submitted to the list. I hope noone disagrees that we need a testsuite. Also, hopefully we all think that a tiny testsuite which is easy to add tests to is much better than a huge project to create a complete testsuite, which never gets started because its too big and scary. I suggest that tests get created whenever someone has a spare moment, or whenever a bug is reported (to replicate the problem, and thus be sure that when fixed it stays fixed), and before making a change to a piece of code to ensure that it remains working. If we all add little tests occasionally, then we'll have a good useful testsuite before we know it. All you need to do is make a
2001-03-09 12:08:38 +00:00
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
tests_pass = test_gst_init
tests_fail =
Makfeile updates. Original commit message from CVS: Makfeile updates.
2001-05-27 22:25:32 +00:00
for better or worse, make distcheck now passes again Original commit message from CVS: for better or worse, make distcheck now passes again
2002-07-01 13:02:03 +00:00
# we makes them, we gots to clean them
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
CLEANFILES += test-registry.xml
hopefully fix distcheck issues Original commit message from CVS: hopefully fix distcheck issues
2002-05-07 03:01:16 +00:00
EXTRA_DIST = gst-inspect-check
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules.
2003-10-15 01:25:41 +00:00
Reference in a new issue Copy permalink