This is a simple autotools example for beginner. You can easily follow it. After that you should be able to use autotools for your own project without complex features. This example shows how to use autoconf/automake, how to edit configure.ac/Makefile.am and how to disable default CFLAGS=’-g -O2’ for debug etc. OK, let’s do it!
autoconf version: 2.68
automake version: 1.11.3
Ubuntu 12.04
Create Sources
If you want to use autotools in your project, first of all you should have an existing one. following is an example I use.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | |
you can DOWNLOAD this project. Of course, you can create your own project.
Autoconf
Generating configure.ac In summary-1.0.0, Use autoscan
airead@airead:/tmp/summary-1.0.0$ ls
doc man script src
airead@airead:/tmp/summary-1.0.0$ autoscan
airead@airead:/tmp/summary-1.0.0$ ls
autoscan.log configure.scan doc man script src
airead@airead:/tmp/summary-1.0.0$
airead@airead:/tmp/summary-1.0.0$ mv configure.scan configure.ac
airead@airead:/tmp/summary-1.0.0$ ls
autoscan.log configure.ac doc man script src
autoscan produces two files autoscan.log and configure.scan. Then we rename configure.scan to configure.ac which will be used by autoconf.
The configure is not perfect, so we should edit it.
1 2 3 4 | |
Generating configure, Use autoconf
airead@airead:/tmp/summary-1.0.0$ ls
autoscan.log configure.ac doc man script src
airead@airead:/tmp/summary-1.0.0$ autoconf
airead@airead:/tmp/summary-1.0.0$ ls
autom4te.cache configure doc script
autoscan.log configure.ac man src
autoconf produces shell script configure used by user and autom4te.cache which you can safely remove it. We already have configure, but where is the Makefile?
Automake
The Relationship Between Makefile.am, Makefile.in And Makefile
Makefile.am is a programmer-defined file and is used by automake to generate the Makefile.in file. The ./configure script will use the Makefile.in to generate a Makefile.
Create Makefile.am
We now prepare the Makefile.am file for each of directories. Automake will step into each of them and produce the corresponding Makefile.in file.
airead@airead:/tmp/summary-1.0.0$ vim Makefile.am
1 2 | |
the first line sets automake mode. “foreign” means not GNU, and is common for avoiding boring messages about files organized differently from what gnu expects.
The second line shows a list of subdirectories to descend for further work.
airead@airead:/tmp/summary-1.0.0$ vim man/Makefile.am
1
| |
In general, the uppercase, suffix part like “_PROGRAMS” is called primary and tells partially what to perform on the argument; the lowecase, prefix (it’s not given a name) tells the directory where to install. So man_MANS installs manuals at $(PREFIX)/share/man.
airead@airead:/tmp/summary-1.0.0$ vim script/Makefile.am
1
| |
installs scripts in $(PREFIX)/bin
airead@airead:/tmp/summary-1.0.0$ vim doc/Makefile.am
1 2 | |
if “abc” is wanted for prefix, “abcdir” is to be specified. E.g. the code above expands to $(PREFIX)/share/doc/summary (“@PACKAGE@” will be expanded by autoconf when producing the final Makefile, see below). $(datadir) is known by all configure scripts it generates, $(PREFIX)/share.
Now let’s create src/Makefile.am, it’s a little complex.airead@airead:/tmp/summary-1.0.0$ vim src/Makefile.am
1
| |
it shows a list of subdirectories to descend for further work. Continue to create…
airead@airead:/tmp/summary-1.0.0$ vim src/lib/Makefile.am
1 2 | |
The special prefix noinst_ indicates that the objects in question should be built but not installed at all. Each _LIBRARIES variable is a list of the libraries to be built. So noinst_LIBRARIES build libutils.a but not install. _SOURCES list sources of libutils.a.
Extra objects can be added to a library using the library_LIBADD variable.
airead@airead:/tmp/summary-1.0.0$ vim src/person/Makefile.am
1 2 3 4 5 | |
Variables that end with _PROGRAMS are special variables that list programs that the resulting Makefile should build. bin_PROGRAMS indicates that program summary should be built and install in $(PREFIX)/bin. its sources shows in summary_LDADD. summary_LDADD indicates that the program needs libutils.a when linking.
Generating Makefile.in, Use automake
let’s run automake:airead@airead:/tmp/summary-1.0.0$ automake
configure.ac: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal).
automake: no `Makefile.am' found for any configure output
automake: Did you forget AC_CONFIG_FILES([Makefile]) in configure.ac?
So we should edit configure.ac again. add following after AC_INIT() in configure.ac.
1
| |
Integrating The Checking (Autoconf) Part And The Building (Automake) Part
Now there are some new Makefile.am in each of directories, so we should reautoscan for extra information in the project.
airead@airead:/tmp/summary-1.0.0$ autoscanairead@airead:/tmp/summary-1.0.0$ diff configure.ac configure.scan
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | |
we found that the configure.ac misses the AC_CONFIG_FILES([*]), so put those above AC_OUTPUT in configure.ac. after that, run following command:
airead@airead:/tmp/summary-1.0.0$ aclocal
airead@airead:/tmp/summary-1.0.0$ autoheader
airead@airead:/tmp/summary-1.0.0$ autoconf
aclocal program creates the file ‘aclocal.m4’ by combining stock installed macros, user defined macros and the contents of ‘acinclude.m4’ to define all of the macros required by ‘configure.ac’ in a single file.
autoheader runs m4 over ‘configure.ac’, but with key macros defined differently than when autoconf is executed, such that suitable cpp definitions are output to ‘config.h.in’.
autoconf expands the m4 macros in ‘configure.ac’, perhaps using macro definitions from ‘aclocal.m4’, to generate the configure script.
Then we call automake to generate Makefile.in.airead@airead:/tmp/summary-1.0.0$ automake --add-missing
configure.ac:9: installing `./install-sh'
configure.ac:9: installing `./missing'
src/lib/Makefile.am:1: library used but `RANLIB' is undefined
src/lib/Makefile.am:1: The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
src/lib/Makefile.am:1: to `configure.ac' and run `autoconf' again.
src/lib/Makefile.am: installing `./depcomp'
Read the error information and fix it by puting AC_PROG_RANLIB after AC_INIT_AUTOMAKE() in configure.ac. run automake again.
airead@airead:/tmp/summary-1.0.0$ automake
Now we have one usable configure script.
Build Project
airead@airead:/tmp/summary-1.0.0$ ./configure
configure do two things:
- scan for dependencies on the basis of the AC_* macros instructed in configure.ac. If there’s something wrong/missing in the system, an opportune error message will be dumped.
- for each Makefile requested in AC_OUTPUT(), translate the Makefile.in template for generating the final Makefile. The main makefile will provide the most common targets like install, clean, distclean, uninstall et al.
If configure succeeds, all the Makefile files are available. Run make.airead@airead:/tmp/summary-1.0.0$ make
If no accident, make will products src/lib/libutils.a and src/person/summary which we can execute. Run following if you like.
airead@airead:/tmp/summary-1.0.0$ make install
Change Default CFLAGS For Debug
autoconf default CFLAGS is ‘-g -O2’, it is inconvenient to debug program. How to change this?
Macro AC_PROG_CC in configure.ac determines a C compiler to use. If using the GNU C compiler, set shell variable GCC to ‘yes’. If output variable CFLAGS was not already set, set it to ‘-g -O2’ for the GNU C compiler (‘-O2’ on systems where GCC does not accept ‘-g’), or ‘-g’ for other compilers.
Put CFLAGS="-g -O0" above AC_PROG_CC, then
airead@airead:/tmp/summary-1.0.0$ autoreconf
It works well.
note: There is no space on either side of =.
扫一扫
1272
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
