July 8, 2007 Jim Huang (jserv)

Size: px

Start display at page:

Download "July 8, 2007 Jim Huang (jserv)"

Morgan Merritt
6 years ago
Views:

1 Introduction to Autotools July 8, 2007 Jim Huang (jserv)

2 Overview Autoconf, Automake, and libtool working together Address portability, configuration needs Support GNU Coding Standards Provide consistent user experience Very popular in Free/Open Source World

3 The Bad Old Days 1990 Edit Makefile Edit source Build No make install

4 Handy Quote It it easier to write a portable shell than to write a portable shell script. Larry Wall

5 Useful tools colormake make with colorful decoration remake modified version of GNU make with debugging and tracing support

6 The real Problem How do we handle platform specific issues? Providing a different Makefile for each architecture Using Autoconf, Automake and Libtool The installer needs only Bourne shell C compilers Make program

7 Some advantages when using GNU autotools The installation of a program is straightforward:./configure; make; make install This procedure checks for system parameters, libraries, location of programs, availability of functions and writes a Makefile./configure supports many options to overwrite defaults settings

8 Development Use Cases

9 GNU toolchain flow (simplified) Developer User configure.in autoconf automake configure Makefile.in./configure Check for required libraries Generate Makefile Makefile.am Makefile

10 Autotools Overview (no libtool) Starting, occasional Under source control Source files [autoscan] [configure.scan] configure.ac Developer, on development system configure.ac [acinclude.m4] Makefile.am autoconf [autoheader] automake configure [config.h.in] Makefile.in distribute Installer, on target system configure [config.h.in] Makefile.in config.cache config.log config.status Source files [config.h] Makefile make End User Executables, libraries, documents, etc.

11 GNU autoconf Source Code configure.ac (configure.in) aclocal autoscan autoconf configure.scan configure

12 GNU automake Makefile.am Makefile.in automake configure Makefile

13 Autoconf(1) Preprocessor based on m4 Turns configure.ac into configure World's most insane shell scripts But portable ones!

14 Autoconf(2) Some philosophy Feature tests, not platform tests The programmer makes the code portable The programmer decides what matters

15 Autoconf(3) Test what is on the actual machine Write conclusions into text files Makefile, config.h, etc Uniform command line options Standard directories like bindir, includedir Large, extensible library of tests

16 Autoconf Example AC_INIT([amhello], [1.0], [bug AM_INIT_AUTOMAKE([ Wall Werror]) AC_PROG_CC AC_CHECK_LIB(z, deflate) AC_CHECK_HEADERS([unistd.h bstring.h]) AC_CONFIG_HEADERS([config.h]) AC_CONFIG_FILES([Makefile]) AC_OUTPUT

17 Boilerplate AC_INIT([amhello], [1.0], [bug AM_INIT_AUTOMAKE([ Wall Werror]) AC_PROG_CC AC_CHECK_LIB(z, deflate) AC_CHECK_HEADERS([unistd.h bstring.h]) AC_CONFIG_HEADERS([config.h]) AC_CONFIG_FILES([Makefile]) AC_OUTPUT

18 Program Checks AC_INIT([amhello], [1.0], [bug AM_INIT_AUTOMAKE([ Wall Werror]) AC_PROG_CC AC_CHECK_LIB(z, deflate) AC_CHECK_HEADERS([unistd.h bstring.h]) AC_CONFIG_HEADERS([config.h]) AC_CONFIG_FILES([Makefile]) AC_OUTPUT

19 Library Checks AC_INIT([amhello], [1.0], [bug AM_INIT_AUTOMAKE([ Wall Werror]) AC_PROG_CC AC_CHECK_LIB(z, deflate) Adds lz to LIBS; defines HAVE_LIBZ AC_CHECK_HEADERS([unistd.h bstring.h]) AC_CONFIG_HEADERS([config.h]) AC_CONFIG_FILES([Makefile]) AC_OUTPUT

20 Header Checks AC_INIT([amhello], [1.0], [bug AM_INIT_AUTOMAKE([ Wall Werror]) AC_PROG_CC AC_CHECK_LIB(z, deflate) AC_CHECK_HEADERS([unistd.h bstring.h]) defines HAVE_UNISTD_H, HAVE_BSTRING_H AC_CONFIG_HEADERS([config.h]) AC_CONFIG_FILES([Makefile]) AC_OUTPUT

21 Automake Support GNU Coding Standards Make common things simple Automate some difficult things Turns Makefile.am into Makefile.in Unrecognized input passed through

22 Automake Features(1) Low cost, precise automatic dependency tracking Non srcdir builds dist/distcheck Various clean targets install/uninstall Parallel builds

23 Automake Features(2) DESTDIR Hooks Platform integration

24 Automake Example bin_programs = hello hello_sources = hello.c

25 Install Directory(1) bin_programs = hello hello_sources = hello.c

26 Install Directory(2) You can make your own directories mylibdir = $(libdir)/whatever mylib_programs = echo

27 Primary(1) bin_programs = hello hello_sources = hello.c

28 Primary(2) There are many primaries PROGRAMS, LIBRARIES, LTLIBRARIES, LISP, PYTHON, JAVA, SCRIPTS, DATA, HEADERS, MANS, TEXINFOS You won't use most of them Other prefixes control semantics: nobase, nodist nobase_nodist_include_headers = foo/foo.h

29 Object Naming(1) bin_programs = hello hello_sources = hello.c

30 Object Naming(2) Names are made make friendly by automake Weird characters are turned to _

31 Object Suffix(1) bin_programs = hello hello_sources = hello.c

32 Object Suffix(2) Object suffixes depend on the type of object Typical ones: SOURCES, CFLAGS, LDFLAGS SOURCES handles many languages C, C++, Yacc, Lex, assembly, Fortran, Java (with gcj) Also header files

33 Libtool Portable creation of shared libraries Integration with autoconf and automake Side features libltdl Convenience libraries

34 Libtool Example(1) configure.ac: AC_PROG_LIBTOOL That's it!

35 Libtool Example(2) lib_ltlibraries = libexample.la libexample_la_sources = src/example1.c x2.c

36 URLs Google Alexandre Duret Lutz archive.cryp.to/

Autotools and GNU Build system

Autotools and GNU Build system YAKA 2008 EPITA 12/12/2006 YAKA 2008 (EPITA) Autotools and GNU Build system Page 1 / 13 Licence Copying is allowed Copyright c 2006 Benoit Sigoure Copyright c 2006 Alexandre