docs/manual/adding-packages-autotools.txt

1 // -*- mode:doc; -*-
4 === Infrastructure for autotools-based packages
6 [[autotools-package-tutorial]]
8 ==== +autotools-package+ tutorial
10 First, let's see how to write a +.mk+ file for an autotools-based
13 ------------------------
21 08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
25 12: LIBFOO_CONF_OPTS = --disable-shared
26 13: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf
28 15: $(eval $(autotools-package))
29 ------------------------
33 On line 8 and 9, we declare the name of the tarball (xz-ed tarball recommended)
38 directory. The staging directory, located in +output/staging/+
39 is the directory where all the packages are installed, including their
41 staging directory, since usually, only libraries need to be installed in
42 the staging directory: their development files are needed to compile
48 target directory. This directory contains what will become the root
50 not necessary to install them in the target directory because they will
62 Finally, on line line 15, we invoke the +autotools-package+
66 [[autotools-package-reference]]
68 ==== +autotools-package+ reference
71 +autotools-package+. It is similar to the +generic-package+ macro. The ability to
73 +host-autotools-package+ macro.
77 +autotools-package+ macro.
120   Makefile.in files should be re-generated by re-running autoconf,
143   default, '-f'.
146   patch to fix libtool cross-compilation issues should be applied or
151   used to install the package to the staging directory. By default, the
157   used to install the package to the target directory. By default, the
164 well for most autotools-based packages. However, when required, it is
167 * By adding a post-operation hook (after extract, patch, configure,