* modules/gnumakefile [Makefile.am]: The makefiles generated by
Automake-NG always contain a definition of VPATH, even in non-VPATH
builds (its value being simply '.' in that case). So, in the
'clean-GNUmakefile' rule, to determine whether running under a
VPATH setup, compare '$(srcdir)' to '.' rather than checking whether
'$(VPATH)' expands to the empty string.
+2012-08-02 Stefano Lattarini <stefano.lattarini@gmail.com>
+
+ gnumakefile: better interaction with Automake-NG
+ * modules/gnumakefile [Makefile.am]: The makefiles generated by
+ Automake-NG always contain a definition of VPATH, even in non-VPATH
+ builds (its value being simply '.' in that case). So, in the
+ 'clean-GNUmakefile' rule, to determine whether running under a
+ VPATH setup, compare '$(srcdir)' to '.' rather than checking whether
+ '$(VPATH)' expands to the empty string.
+
2012-08-02 Carlo de Falco <carlo.defalco@polimi.it> (tiny change)
base64: Use extern C scope in header file, for C++.
Makefile.am:
distclean-local: clean-GNUmakefile
clean-GNUmakefile:
- test x'$(VPATH)' != x && rm -f $(top_builddir)/GNUmakefile || :
+ test '$(srcdir)' = . || rm -f $(top_builddir)/GNUmakefile
Include: