From: Stefano Lattarini Date: Fri, 26 Oct 2012 18:18:51 +0000 (+0200) Subject: news: update w.r.t. recent vala changes X-Git-Tag: v1.12.5~11^2~1 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0e3d9b3e3ca9bf308c6f10b3ff3189955e208b66;p=platform%2Fupstream%2Fautomake.git news: update w.r.t. recent vala changes * NEWS: Here. Signed-off-by: Stefano Lattarini --- diff --git a/NEWS b/NEWS index 1c8c401..6377234 100644 --- a/NEWS +++ b/NEWS @@ -61,6 +61,30 @@ New in 1.12.5: giving more useful warnings than a bare "command not found" from a make recipe would. +* Vala support: + + - The AM_PROG_VALAC macro has been enhanced to takes two further + optional arguments; it's signature now being + + AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND], + [ACTION-IF-NOT-FOUND]) + + - By default, AM_PROG_VALAC no longer aborts the configure invocation + if the Vala compiler found is too old, but simply prints a warning + messages (as it did when the Vala compiler was not found). This + should avoid unnecessary difficulties for end users that just want + to compile the unmodified, distributed Vala-generated C sources, + but happens to have an old Vala compiler in their PATH. This fixes + automake bug#12688. + + - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC + will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'. + This is a better default, because with it a triggered makefile rule + invoking a Vala compilation will clearly fail with an informative error + message like "valac: command not found", rather than silently, with + the error possibly going unnoticed or triggering harder-to-diagnose + fallout failures in later steps. + Bugs fixed in 1.12.5: * Long-standing bugs: