isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-11 22:10:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
1ff3011cb7
mutter/tests/performance/Makefile.am

45 lines
1.1 KiB
Makefile
Raw Normal View History

tests: Add performance tracking framework This adds a performance tracking framework that can run a set of tests over specified git revisions. The ruby script for generating the reports comes from similar performance tracking in GEGL. The framework permits evaluating new tests against older version of clutter. The tests themselves go through a few hoops for disabling framerate limiting in both mesa and clutter. When running make check the tests will be run and lines of the form: @ test-state: 40.51 fps will be left in the output, a script can scrape these lines out of a build log on a buildbot to in other ways track performance.
2011-01-19 11:38:25 +00:00
include $(top_srcdir)/build/autotools/Makefile.am.silent
noinst_PROGRAMS = \
test-picking \
test-text-perf \
test-state \
test-state-interactive \
test-state-hidden \
test-state-mini \
test-state-pick
INCLUDES = \
build: Fix out of tree builds
2012-07-30 11:33:24 +00:00
-I$(top_srcdir) \
-I$(top_builddir) \
tests: Add performance tracking framework This adds a performance tracking framework that can run a set of tests over specified git revisions. The ruby script for generating the reports comes from similar performance tracking in GEGL. The framework permits evaluating new tests against older version of clutter. The tests themselves go through a few hoops for disabling framerate limiting in both mesa and clutter. When running make check the tests will be run and lines of the form: @ test-state: 40.51 fps will be left in the output, a script can scrape these lines out of a build log on a buildbot to in other ways track performance.
2011-01-19 11:38:25 +00:00
-I$(top_srcdir)/clutter \
build: Add -lm to the tests linker flags https://bugzilla.gnome.org/show_bug.cgi?id=657529
2011-08-27 22:58:26 +00:00
-I$(top_builddir)/clutter
Implement multi-backend support The Clutter backend split is opaque enough that should allow us to just build all possible backends inside the same shared object, and select the wanted backend at initialization time. This requires some work in the build system, as well as the initialization code, to remove duplicate functions that might cause conflicts at build and link time. We also need to defer all the checks of the internal state of the platform-specific API to run-time type checks.
2011-09-21 17:05:03 +00:00
common_ldadd = $(top_builddir)/clutter/libclutter-@CLUTTER_API_VERSION@.la
build: Add -lm to the tests linker flags https://bugzilla.gnome.org/show_bug.cgi?id=657529
2011-08-27 22:58:26 +00:00
LDADD = $(common_ldadd) $(CLUTTER_LIBS) -lm
tests: Add performance tracking framework This adds a performance tracking framework that can run a set of tests over specified git revisions. The ruby script for generating the reports comes from similar performance tracking in GEGL. The framework permits evaluating new tests against older version of clutter. The tests themselves go through a few hoops for disabling framerate limiting in both mesa and clutter. When running make check the tests will be run and lines of the form: @ test-state: 40.51 fps will be left in the output, a script can scrape these lines out of a build log on a buildbot to in other ways track performance.
2011-01-19 11:38:25 +00:00
AM_CFLAGS = \
$(CLUTTER_CFLAGS) \
-DG_DISABLE_SINGLE_INCLUDES \
build: Disable deprecation warnings in tests/performance
2011-12-06 17:53:37 +00:00
-DGLIB_DISABLE_DEPRECATION_WARNINGS \
-DCLUTTER_DISABLE_DEPRECATION_WARNINGS \
tests: Add performance tracking framework This adds a performance tracking framework that can run a set of tests over specified git revisions. The ruby script for generating the reports comes from similar performance tracking in GEGL. The framework permits evaluating new tests against older version of clutter. The tests themselves go through a few hoops for disabling framerate limiting in both mesa and clutter. When running make check the tests will be run and lines of the form: @ test-state: 40.51 fps will be left in the output, a script can scrape these lines out of a build log on a buildbot to in other ways track performance.
2011-01-19 11:38:25 +00:00
-DTESTS_DATA_DIR=\""$(top_srcdir)/tests/data/"\"
perf-report: check
check:
for a in $(noinst_PROGRAMS);do ./$$a;done;true
test_picking_SOURCES = test-picking.c
test_text_perf_SOURCES = test-text-perf.c
test_state_SOURCES = test-state.c
test_state_hidden_SOURCES = test-state-hidden.c
test_state_pick_SOURCES = test-state-pick.c
test_state_interactive_SOURCES = test-state-interactive.c
test_state_mini_SOURCES = test-state-mini.c
EXTRA_DIST = Makefile-retrospect Makefile-tests create-report.rb test-common.h
-include $(top_srcdir)/build/autotools/Makefile.am.gitignore
Reference in New Issue Copy Permalink