Changed root Makefile.in to Makefile.am, which make autoreconf workable

Running autoreconf without errors, and using a custom autoconf directory, means that automake features are used, in order to find that autoconf directory. This cleans up the root build system to make it less surprising to maintainers.
tklauser · Jun 13, 2011 · ef1f0d4 · ef1f0d4
1 parent e0adfa6
commit ef1f0d4
Show file tree

Hide file tree

Showing 8 changed files with 16 additions and 309 deletions.
diff --git a/AUTHORS b/AUTHORS
diff --git a/COPYING b/COPYING
@@ -0,0 +1 @@
+COPYRIGHT
diff --git a/Makefile.am b/Makefile.am
@@ -0,0 +1,14 @@
+DISTCHECK_CONFIGURE_FLAGS =
+
+ACLOCAL_FLAGS = -I autoconf
+ACLOCAL_AMFLAGS = -I autoconf
+
+#PACKAGE_NAME	= @PACKAGE_NAME@
+#PACKAGE_VERSION	= @PACKAGE_VERSION@
+
+@ENCAP_DEFS@
+
+#@SET_MAKE@
+
+SUBDIRS = lib libtar doc
+
diff --git a/Makefile.in b/Makefile.in
diff --git a/NEWS b/NEWS
diff --git a/autoconf/install-sh b/autoconf/install-sh
diff --git a/autogen.sh b/autogen.sh
diff --git a/configure.ac b/configure.ac
@@ -10,6 +10,7 @@ All rights reserved.
 ]])
 AC_CONFIG_SRCDIR([lib/libtar.h])
 AC_CONFIG_MACRO_DIR([autoconf])
+AM_INIT_AUTOMAKE([dist-bzip2])
 ENCAP_PKG([], [postinstall-encap])