mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-26 10:10:32 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/testsuite/Makefile.am

30 lines
797 B
Makefile
Raw Normal View History

re-enable thread test, although it does not work but passes right now warn for bizarre behavior in plugin loading Original commit message from CVS: re-enable thread test, although it does not work but passes right now warn for bizarre behavior in plugin loading
2002-05-25 17:45:51 +00:00
# FIXME : threads bytestream
dist fixes Original commit message from CVS: dist fixes
2002-07-01 12:08:22 +00:00
SUBDIRS = caps plugin elements clock refcounting ## cleanup dynparams
Fix the tests so that builds that are not --enable-plugin-builddir can register the plugins from the uninstalled gstr... Original commit message from CVS: Fix the tests so that builds that are not --enable-plugin-builddir can register the plugins from the uninstalled gstreamer directory. There is some small amount of voodoo here. Also, add gst-inspect-check to gstreamer/testsuite, where it probably belongs
2002-05-05 16:49:45 +00:00
GST_PLUGIN_PATH = $(shell cd $(top_builddir) && pwd)
TESTS_ENVIRONMENT = GST_PLUGIN_PATH=$(GST_PLUGIN_PATH) GST_REGISTRY=`pwd`/test-registry.xml
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
fixing tests Original commit message from CVS: fixing tests
2002-07-01 10:41:39 +00:00
if BUILD_FAILING_TESTS
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
testprogs = test_gst_init
fixing tests Original commit message from CVS: fixing tests
2002-07-01 10:41:39 +00:00
inspectcheck = gst-inspect-check
else
testprogs =
inspectcheck =
endif
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
fixing tests Original commit message from CVS: fixing tests
2002-07-01 10:41:39 +00:00
TESTS = $(top_builddir)/tools/gst-register $(testprogs) $(inspectcheck)
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
check_PROGRAMS = $(testprogs)
# we have nothing but apps here, we can do this safely
- some fixes to int2float making automake 1.5 happy (gst now requires automake1.5). It's still not perfect but it bui... Original commit message from CVS: - added playondemand plugin by Leif Morgan Johnson <lmjohns3@eos.ncsu.edu> - some fixes to int2float - aplied a patch from wrobell <wrobell@ite.pl> that is a first attempt at making automake 1.5 happy (gst now requires automake1.5). It's still not perfect but it builds. - Made the schedulers plugable. The default scheduler now lives inside a plugin. - Added a new mpeg1/2 parser/demuxer. - Fixed some compiler warnings in the core libs. - substantial work to GstThread (hopefully less race conditions). simplified the code in GstThread a bit. A state change can now also happen in the thread context. - reworked the state semantics of a bin. it'll now automatically get the highest state of its children. - the autoplugger now nests the threads so that a state change failure of one thread doesn't make its upstream thread lock. - GstQueue refuses to go to PLAYING if the sinkpad is not connected. This way the queue will not wedge in the _get lock. - GstQueue unlocks its mutexes when going to PAUSED. - make sure that when all elements in a bin/thread go to PAUSED, the bin is set to PAUSED too. - make a parent bin wait for its children to PAUSE before ending the iteration with FALSE (EOS) - Some changes to GstPlay to deal with EOS. - aplied the latest patch from Zeenix to gstrtp. end result: GstPlay doesn't crash on EOS and the pipeline is now shut down properly.
2001-12-04 22:12:50 +00:00
LIBS = $(GST_LIBS)
use AM_CFLAGS instead of CFLAGS Original commit message from CVS: use AM_CFLAGS instead of CFLAGS
2002-11-02 05:24:27 +00:00
AM_CFLAGS = $(GST_CFLAGS)
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
CLEANFILES = test-registry.xml elementstest-registry.xml
various more tests enabling Original commit message from CVS: various more tests enabling
2002-05-09 16:44:22 +00:00
DIST_SUBDIRS = bytestream caps cleanup clock dynparams elements \
re-enable thread test, although it does not work but passes right now warn for bizarre behavior in plugin loading Original commit message from CVS: re-enable thread test, although it does not work but passes right now warn for bizarre behavior in plugin loading
2002-05-25 17:45:51 +00:00
plugin refcounting threads
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
Reference in a new issue Copy permalink