isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-18 09:02:04 +00:00
Code Issues Packages Projects Releases Wiki Activity
0be812161e
mutter/clutter/tests/performance/Makefile.am

44 lines
1.2 KiB
Makefile
Raw Normal View History

build: Ensure tests are built only on make check Tests should only be enabled when we want to run them, or when we are generating a tarball.
2013-08-16 09:57:54 +00:00
check_PROGRAMS = \
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
test-picking \
test-text-perf \
test-state \
test-state-interactive \
test-state-hidden \
test-state-mini \
test-state-pick
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 16:16:07 +00:00
common_ldadd = $(top_builddir)/clutter/libmutter-clutter-@LIBMUTTER_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
build: Use libtool macros to find libm Instead of using `-lm` everywhere, use LT_LIB_M inside configure.ac, and $(LIBM) inside Makefile.am.
2015-03-03 17:23:37 +00:00
LDADD = $(common_ldadd) $(CLUTTER_LIBS) $(LIBM)
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
build: Remove INCLUDES directives They have been deprecated for a while, replaced by AM_CPPFLAGS.
2013-05-15 14:18:13 +00:00
AM_CFLAGS = $(CLUTTER_CFLAGS)
AM_CPPFLAGS = \
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
-DG_DISABLE_SINGLE_INCLUDES \
build: Disable deprecation warnings in tests/performance
2011-12-06 17:53:37 +00:00
-DGLIB_DISABLE_DEPRECATION_WARNINGS \
build: Disable Cogl deprecation warnings for tests We are exercising all sorts of deprecated API anyway.
2013-07-02 21:24:31 +00:00
-DCOGL_DISABLE_DEPRECATION_WARNINGS \
build: Disable deprecation warnings in tests/performance
2011-12-06 17:53:37 +00:00
-DCLUTTER_DISABLE_DEPRECATION_WARNINGS \
build: Remove INCLUDES directives They have been deprecated for a while, replaced by AM_CPPFLAGS.
2013-05-15 14:18:13 +00:00
-DTESTS_DATA_DIR=\""$(top_srcdir)/tests/data/"\" \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 17:58:20 +00:00
-I$(top_srcdir)/../cogl \
-I$(top_builddir)/../cogl \
build: Fix cogl include paths of tests Those were missed by commit 0aa6d9782c6 ...
2016-11-23 22:12:21 +00:00
-I$(top_builddir)/../cogl/cogl \
build: Remove INCLUDES directives They have been deprecated for a while, replaced by AM_CPPFLAGS.
2013-05-15 14:18:13 +00:00
-I$(top_srcdir) \
-I$(top_builddir) \
-I$(top_srcdir)/clutter \
-I$(top_builddir)/clutter
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
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
Reference in New Issue Copy Permalink