build: Use target-specific VALAFLAGS rather than AM_VALAFLAGS
authorPhilip Withnall <philip@tecnocode.co.uk>
Thu, 20 Jun 2013 16:21:41 +0000 (17:21 +0100)
committerPhilip Withnall <philip@tecnocode.co.uk>
Fri, 5 Jul 2013 20:46:22 +0000 (21:46 +0100)
commit037caf3a4d1d1b8de5fb6c4d78887793f36700a8
treef03501c7b21639cd913384e58c639e59ee73e5d8
parent8ebe13c457660de380521874a006425083151741
build: Use target-specific VALAFLAGS rather than AM_VALAFLAGS

This allows automake to parse the flags for each target and generate
appropriate rules. For example, by explicitly specifying “--vapi foo.vapi” in
foo_VALAFLAGS (not just specifying “--library foo”), dependency and clean-up
rules for foo.vapi will be generated by automake. Accordingly, this commit
also adds missing --vapi flags.

Helps: https://bugzilla.gnome.org/show_bug.cgi?id=701099
16 files changed:
backends/eds/Makefile.am
backends/eds/lib/Makefile.am
backends/libsocialweb/Makefile.am
backends/libsocialweb/lib/Makefile.am
backends/telepathy/Makefile.am
backends/telepathy/lib/Makefile.am
backends/tracker/Makefile.am
backends/tracker/lib/Makefile.am
folks/Makefile.am
tests/lib/Makefile.am
tests/lib/eds/Makefile.am
tests/lib/key-file/Makefile.am
tests/lib/libsocialweb/Makefile.am
tests/lib/telepathy/Makefile.am
tests/lib/tracker/Makefile.am
tests/telepathy/Makefile.am