LADI
/
clutter
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
clutter/Makefile.am

66 lines
1.9 KiB
Makefile
Raw Normal View History

[build] Split out the custom silent rules The silent rules we use for custom targets should be moved into a separate Makefile.am that gets included from all the others.
2009-09-16 19:43:58 +03:00
include $(top_srcdir)/build/autotools/Makefile.am.silent
2008-01-25 Emmanuele Bassi <ebassi@openedhand.com> * clutter/x11/Makefile.am: Add the generated clutter-x11 pkg-config file to CLEANFILES, to pass distcheck. * Makefile.am: * clutter/Makefile.am: Tweak up the Makefiles. * README: * NEWS: Release 0.5.4 * configure.ac: Post-release bump to 0.5.5
2008-01-25 21:48:26 +02:00
NULL =
Fully rework the conformance test suite The current conformance test suite is suboptimal in many ways. All tests are built into the same binary, which makes adding new tests, builting tests, and running groups of tests much more awkward than it needs to be. The first issue, especially, raises the bar of contribution in a significant way, while the other two take their toll on the maintainer. All of these changes were introduced back when we had both Clutter and Cogl tests in tree, and because we were building the test suite for every single change; since then, Cogl moved out of tree with all its tests, and we build the conformance test suite only when running the `check` make target. This admittedly large-ish commit changes the way the conformance test suite works, taking advantage of the changes in the GTest API and test harness. First of all, all tests are now built separately, using their own test suite as defined by each separate file. All tests run under the TAP harness provided by GTest and Automake, to gather a proper report using the Test Anything Protocol without using the `gtester` harness and the `gtester-report` script. We also use the Makefile rules provided by GLib to vastly simplify the build environment for the conformance test suite. On top of the changes for the build and harness, we also provide new API for creating and running test suites for Clutter. The API is public, because the test suite has to use it, but it's minimal and mostly provides convenience wrappers around GTest that make writing test units for Clutter easier. This commit disables all tests in the conformance test suite, as well as moving the data files outside of the tests/data directory; the next few commits will re-establish the conformance test suite separately so we can check that everything works in a reliable way.
2013-12-12 16:36:16 +02:00
SUBDIRS = build clutter tests doc po
build: Allow disabling all tests and examples This should allow nicer build automation and cross-compilation support. The former --disable-conformance configure switch has been deprecated by the --disable-tests one, which is more encompassing as it disables the whole test suite.
2012-05-01 20:51:19 +03:00
if BUILD_EXAMPLES
SUBDIRS += examples
endif
DIST_SUBDIRS = clutter tests examples doc po build
And finish the move
2006-06-23 13:42:29 +03:00
build: Sanitize the hack for ACLOCAL_FLAGS Move the ACLOCAL_FLAGS hack we have to use with jhbuild and autoreconf inside the ACLOCAL_AMFLAGS declaration in Makefile.am, and leave autogen.sh alone.
2010-11-11 14:03:24 +02:00
# XXX - this is a massive hack to make autoreconf honour the ACLOCAL_FLAGS
# that jhbuild sets while still retaining build/autotools as the authoritative
# source for m4 macros
ACLOCAL_AMFLAGS = -I build/autotools ${ACLOCAL_FLAGS}
[build] Beautify autotools' output Use shave (http://git.lespiau.name/cgit/shave) to make compilation more human friendly.
2009-02-17 16:56:35 +02:00
build: Start moving to a non-recursive layout *** WARNING: THIS COMMIT CHANGES THE BUILD *** Do not recurse into the backend directories to build private, internal libraries. We only recurse from clutter/ into the cogl sub-directory; from there, we don't recurse any further. All the backend-specific code in Cogl and Clutter is compiled conditionally depending on the macros defined by the configure script. We still recurse from the top-level directory into doc, clutter and tests, because gtk-doc and tests do not deal nicely with non-recursive layouts. This change makes Clutter compile slightly faster, and cleans up the build system, especially when dealing with introspection data. Ideally, we also want to make Cogl part of the top-level build, so that we can finally drop the sed trick to change the shared library from the GIR before compiling it. Currently disabled: ‣ OSX backend ‣ Fruity backend Currently enabled but untested: ‣ EGL backend ‣ Windows backend
2010-09-13 13:30:30 +03:00
EXTRA_DIST = \
build: Fix EXTRA_DIST and MAINTAINERCLEANFILES rules
2009-11-18 17:21:09 +02:00
ChangeLog.pre-git-import \
build: Add README template to EXTRA_DIST
2011-02-14 19:34:15 +02:00
README.in \
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 12:25:47 +03:00
README \
build: Fix EXTRA_DIST and MAINTAINERCLEANFILES rules
2009-11-18 17:21:09 +02:00
$(NULL)
And finish the move
2006-06-23 13:42:29 +03:00
2007-06-27 Matthew Allum <mallum@openedhand.com> * Makefile.am: Dont remove README on make clean
2007-06-27 14:56:41 +03:00
CLEANFILES = $(pcfiles)
And finish the move
2006-06-23 13:42:29 +03:00
build: Remove dolt remnants We don't use Dolt any more, since we depend on libtool 2.2.
2010-08-17 13:34:35 +03:00
DISTCLEANFILES =
[build] Add automatic ChangeLog generation on dist Since we moved to Git from Subversion we've abandoned the ChangeLog file in favour of a more detailed commit log. In order to maintain a ChangeLog for users of the tarballs, we need to generate a ChangeLog file out of the commit log when distchecking a Clutter release. For this reason, we use a simple Perl script that is invoked by the dist-hook and generates a ChangeLog file starting from the previous stable release.
2009-01-29 17:38:28 +02:00
build: Pass --enable-cookbook when distchecking We should force building the cookbook when releasing a tarball of Clutter, so that users of packaged tarballs can actually build the cookbook themselves.
2011-02-01 16:38:08 +02:00
DISTCHECK_CONFIGURE_FLAGS = --enable-gtk-doc --enable-maintainer-flags --enable-docs
And finish the move
2006-06-23 13:42:29 +03:00
build: Remove maintainer-clean rule The maintainer-clean files list is horribly out of date, nobody is maintaining it, and it's honestly easier to use `git clean -xdf` instead to clean untracked files.
2011-02-22 20:32:01 +02:00
# .release requires .changelog rules
build: Generate per-cycle ChangeLog files We should generate a ChangeLog for each minor version cycle, starting from the Git import date (since before that we used ChangeLog-style commit messages that don't really look good with the Git ones). For this reason we can take Cairo's Makefile.am.changelog file and, after tweaking it to fit our use case, let it generate the correct ChangeLogs on dist.
2009-11-18 16:21:08 +02:00
include $(top_srcdir)/build/autotools/Makefile.am.changelog
build: Automate the release process
2010-10-03 16:53:14 +03:00
include $(top_srcdir)/build/autotools/Makefile.am.release
Add gcov support to the build Using gcov it's possible to get a coverage report, that is a break down of how much the exposed API is exercised by the conformance test suite.
2010-01-04 16:53:03 +02:00
build: Automate the release process
2010-10-03 16:53:14 +03:00
# proxy rules for tests
test-report full-report:
$(MAKE) -C tests/conform $(@)
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 13:38:25 +02:00
perf-report:
$(MAKE) -C tests/performance $(@)
build: Add coverage support using lcov Unlike gcov, lcov provides a nice HTML output that allows immediate visualization of the current coverage. The updates of the build system have been taken from GLib, which has been using lcov for a while with good results.
2012-06-19 16:43:40 +03:00
if ENABLE_GCOV
# use recursive makes in order to ignore errors during check/perf
lcov:
-$(MAKE) $(AM_MAKEFLAGS) -C clutter check
-$(MAKE) $(AM_MAKEFLAGS) -C tests/conform test
$(MAKE) $(AM_MAKEFLAGS) genlcov
# we have to massage the lcov.info file slightly to hide the effect of libtool
# placing the objects files in the .libs/ directory separate from the *.c
genlcov:
$(LTP) --directory $(top_builddir) --capture --output-file clutter-lcov.info --test-name CLUTTER_TEST --no-checksum
$(SED) -e 's#.libs/##' < clutter-lcov.info > clutter-lcov.info.tmp
LANG=C $(LTP_GENHTML) --prefix $(top_builddir) --output-directory clutter-lcov --title "Clutter Code Coverage" --show-details clutter-lcov.info.tmp
rm -f clutter-lcov.info.tmp
lcov-clean:
-$(LTP) --directory $(top_builddir) -z
-$(RM) -rf clutter-lcov.info clutter-lcov
else
lcov genlcov lcov-clean:
@echo You need to configure Clutter with support for gcov enabled.
@echo e.g., ./configure --enable-gcov
endif
.PHONY: test-report full-report perf-report lcov genlcov lcov-clean