brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
24a451b388
mutter/Makefile.am

42 lines
1009 B
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 12:43:58 -04: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 14:48:26 -05:00
NULL =
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
SUBDIRS = clutter tests doc po build
And finish the move
2006-06-23 06:42:29 -04: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 07:03:24 -05: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 09:56:35 -05: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 06:30:30 -04:00
EXTRA_DIST = \
build: Fix EXTRA_DIST and MAINTAINERCLEANFILES rules
2009-11-18 10:21:09 -05:00
ChangeLog.pre-git-import \
build: Add README template to EXTRA_DIST
2011-02-14 12:34:15 -05:00
README.in \
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
README \
config.h.win32 \
config.h.win32.in \
build: Fix EXTRA_DIST and MAINTAINERCLEANFILES rules
2009-11-18 10:21:09 -05:00
$(NULL)
And finish the move
2006-06-23 06:42:29 -04:00
2007-06-27 Matthew Allum <mallum@openedhand.com> * Makefile.am: Dont remove README on make clean
2007-06-27 07:56:41 -04:00
CLEANFILES = $(pcfiles)
And finish the move
2006-06-23 06:42:29 -04:00
build: Remove dolt remnants We don't use Dolt any more, since we depend on libtool 2.2.
2010-08-17 06:34:35 -04: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 10:38:28 -05: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 09:38:08 -05:00
DISTCHECK_CONFIGURE_FLAGS = --enable-gtk-doc --enable-maintainer-flags --enable-docs
And finish the move
2006-06-23 06:42:29 -04: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 13:32:01 -05: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 09:21:08 -05:00
include $(top_srcdir)/build/autotools/Makefile.am.changelog
build: Automate the release process
2010-10-03 09:53:14 -04: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 09:53:03 -05:00
build: Automate the release process
2010-10-03 09:53:14 -04:00
# proxy rule for gcov
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 09:53:03 -05:00
gcov:
@( cd clutter && $(MAKE) $(AM_MAKEFLAGS) $@ ) || exit $$?
build: Automate the release process
2010-10-03 09:53:14 -04: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 06:38:25 -05:00
perf-report:
$(MAKE) -C tests/performance $(@)
.PHONY: gcov test-report full-report perf-report
Reference in New Issue Copy Permalink