Autotools integration
Updated 2,153 Days AgoPublic
Actions

Introduction

This document describes how to use and integrate autotools in EFL projects. It shows the common tree structure directories and it details how to write configure.ac and Makefile.am files. It is not a complete tutorial on the autotools, but it describes basic use, correct usage and some tricks. It also mentions some m4 macros used in the EFL.

Tree Structure

The usual tree directories structure of an EFL program based on the EFL is:

project/
   data/
   doc/
   src/
      bin/
      lib/
      tests/

Some of the subdirectories might not be present (mainly tests subdirectory). For a program, the data/ subdirectory usually contains a theme/ subdirectory, for edc files.

Autoconf

All projects must contain the file configure.ac. This file must be processed by autoconf to produce a configure script file. The main purpose of that script file is to produce Makefile files, but can be used for a lot of other things too.

The file configure.ac is in the subdirectory project/. This file should contain at least the following calls:

Initialization of autoconf (with the name of the project, its version and the mail to report problems to)
Initialization of automake
If the project is a library, initialization of libtool
Check of a compiler (usually a C one like gcc)
Configure the files that the configure script must create (mainly the Makefile files)
Output files

Hence, a very basic configure.ac file is:

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
AC_PROG_LIBTOOL
 
AC_PROG_CC
 
AC_CONFIG_FILES([])
 
AC_OUTPUT

NOTE: Remove AC_PROG_LIBTOOL if the project does not create a library.

To create the configure script file, just run in the directory where configure.ac is located:

autoreconf -f -i

The call AC_CONFIG_FILES should list all the files that configure must create. It transforms a file named Foo.in into Foo and it replaces some parts of text of Foo.in (consider these parts as shell variables) by their value. That's the purpose of the configure script: replacing text by value.

As the main purpose is to create Makefile files with the configure script, AC_CONFIG_FILES must list all the needed Makefile, one for each subdirectory of tree structure. Our configure.ac file is now:

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
AC_PROG_LIBTOOL
 
AC_PROG_CC
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT

So, it will transform all the Makefile.in files into Makefile files. To create Makefile.in files, an easy way is to use automake.

Automake

The purpose of automake is to transform Makefile.am files into Makefile.in files, these latter being transforms by the configure script (see previous section). So we have to create one Makefile.am for each Makefile which is listed in AC_CONFIG_FILES (in configure.ac).

Some Makefile.am are just for going from a directory to a subdirectory. Then, the content of the Makefile.am is just:

SUBDIRS = subdir1 subdir2 subdir3

The order is important. The Makefile file will go first insubdir1, then subdir2, then subdir3, then process the current directory. To process the current directory before one of the sub directory, just use '.' somewhere. For example, if we want to process the current directory before all the subdirectory (for some dependencies reasons), use:

SUBDIRS = . subdir1 subdir2 subdir3

To clean the files correctly, the files Makefile.in must be removed the with maintainer-clean rule. For that, we have to add in each Makefile.am

MAINTAINERCLEANFILES = Makefile.in

Top level Makefile.am

MAINTAINERCLEANFILES = Makefile.in
SUBDIRS = src data doc

Makefile.am in src

MAINTAINERCLEANFILES = Makefile.in
SUBDIRS = lib bin tests

Makefile.am in data

MAINTAINERCLEANFILES = Makefile.in
SUBDIRS = theme

Now, the remaining Makefile.am are data/theme/Makefile.am, doc/Makefile.am, src/bin/Makefile.am, src/lib/Makefile.am and src/tests/Makefile.am.

Libtool, or how to easily create a library

Now, we are going to see how to write src/lib/Makefile.am. In that directory, we consider the 3 files of our library: Foo.h, foo1.c and foo2.c. Foo.h is the exported header files, used for the API of our library. foo1.c and foo2.c contain the definition of the functions declared in Foo.h. We want:

to compile foo1.c and foo2.c and to create libfoo.a and libfoo.so
to install Foo.h

The installation of the library files will be automatic. Here is src/lib/Makefile.am:

MAINTAINERCLEANFILES = Makefile.in
 
include_HEADERS = Foo.h
 
lib_LTLIBRARIES = libfoo.la
 
libfoo_la_SOURCES  = foo1.c foo2.c

So we add to lib_LTLIBRARIES one (or several) library name(s) sufixed by '.la'. For each of these library, we specify all the sources.

The binary

Now, we want to create a binary named bar, which depends on libfoo. It's the same kind of stuff: we specify which program we want to create, and its source files. We suppose that the program bar is composed of 2 files: bar1.c and bar2.c. Here is src/bin/Makefile.am:

MAINTAINERCLEANFILES = Makefile.in
 
bin_PROGRAMS = bar
 
bar_SOURCES  = bar1.c bar2.c
bar_LDADD = $(top_builddir)/src/lib/libfoo.la

Improvements of configure.ac and the Makefile.am's

We can improve configure.ac in several ways. Here are some hints.

Libtool is slooooow

libtool checks for C++ and fortran 77 compiler when the configure script is launched. To remove these checks, we add 2 calls before AC_PROG_LIBTOOL:

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
AC_PROG_LIBTOOL
 
AC_PROG_CC
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT

Versioning of the shared library

It can be convenient to add a version in the shared library. It allow to separate the shared lib from different api (api expansion, api break, etc...). For more details about how to change the version, follow that link. Otherwise, we suppose that our configure.ac defines a variable named version_info, based on the version of the project. The way the version of the project is modified should follow this scheme just before a release:

If bug fixes only, increase micro version (v_mic).
If API is added, increase minor version (v_min) and set micro version to 0 (v_mic).
If API or ABI is modified, increase major version (v_maj) and set minor version (v_min) and micro version (v_mic) both to 0.

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
m4_define([lt_cur], [m4_eval([v_maj] + [v_min])])
m4_define([lt_rev], [v_mic])
m4_define([lt_age], [v_min])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
AC_PROG_LIBTOOL
 
version_info="lt_cur:lt_rev:lt_age"
AC_SUBST([version_info])
 
AC_PROG_CC
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT

and src/lib/Makefile.am is:

MAINTAINERCLEANFILES = Makefile.in
 
include_HEADERS = Foo.h
 
lib_LTLIBRARIES = libfoo.la
 
libfoo_la_SOURCES  = foo1.c foo2.c
libfoo_la_LDFLAGS = -version-info @version_info@

Usage of $prefix based directory

The EFL might use, in his code, a directory which value is based on the value of the variable $prefix in configure (value that can be changed with the --prefix option of configure). For example, all the engines are in a subdif of ${libdir}/evas/modules/engines, and ${libdir} is equal to ${exec_prefix}/lib and ${exec_prefix} is equal to ${prefix}.

The solution would be to pass to the preprocessor the value -DMY_LIB_DIR="${prefix}/lib/***" (so, a string) with AC_DEFINE in the configure.ac file. But, the value of ${prefix} is never defined in the configure script. You can write bad hack to find a solution, but the correct solution is to pass that value in the Makefile (actually, Makefile.am), because, at this "time", the value of {$prefix} is known.

To pass -DMY_LIB_DIR="${prefix}/lib/***" to the preprocessor in Makefile.am, you have 2 solutions:

You can use the variable AM_CPPFLAGS, in that case, all the possible libraries programs that are build by that Makefile.am will have it,
You can pass that value to only the library or program by using the *_CPPFLAGS variable, where the star '*' is the name of the project.

For example, in the first case, our Makefile.am would be:

MAINTAINERCLEANFILES = Makefile.in
 
AM_CPPFLAGS = -DMY_LIB_DIR=\"$(libdir)\"
 
include_HEADERS = Foo.h
 
lib_LTLIBRARIES = libfoo.la
 
libfoo_la_SOURCES  = foo1.c foo2.c
libfoo_la_LDFLAGS = -version-info @version_info@

Note that to have a C string, we must use \", otherwise automake will consider it as a string in your future Makefile.

In the second example, our Makefile.am would be:

MAINTAINERCLEANFILES = Makefile.in
 
include_HEADERS = Foo.h
 
lib_LTLIBRARIES = libfoo.la
 
libfoo_la_SOURCES  = foo1.c foo2.c
libfoo_la_CPPFLAGS = -DMY_LIB_DIR=\"$(libdir)\"
libfoo_la_LDFLAGS = -version-info @version_info@

Also, in configure.ac, we must add AM_PROG_CC_C_O.

These examples were for a library, but it is exactly the same for a binary.

Usage of pkg-config

Your program or library can depend on another library. If that library is sufficiently recent, it has a .pc file and pkg-config can be used to retrieve in a simple way the flags to pass to the preprocessor (all the needed -I and -D gcc options) and the flags to pass to the linker (-L and -l ld options).

Firstly, you have to check if pkg-config exists. Use PKG_PROG_PKG_CONFIG in configure.ac

Secondly, you have to detect the .pc file in configure.ac. Nowadays, all the linux distributions have an m4 macro for that: PKG_CHECK_MODULES. For example, if you want to detect eet, you can use:

PKG_CHECK_MODULES([EET], [eet])

this macro tries to find the file eet.pc (eet because of the second parameter of that macro). If it is found, it puts in the variables EET_CFLAGS and EET_LIBS respectively the -I and -D options, and the -L and -l (and even more, like -pthread, for example) options (EET because of the first parameter of the macro). If eet.pc is not found, the configure scripts aborts and displays an error.

Sometimes, it is useful to not abort (because the library is not a strict dependency, but is instead optional). For that, you just have to use the third or fourth parameters. Another interest to use them is to display if eet is available or not. So, in that case, our configure.ac is then:

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
m4_define([lt_cur], [m4_eval([v_maj] + [v_min])])
m4_define([lt_rev], [v_mic])
m4_define([lt_age], [v_min])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
AC_PROG_LIBTOOL
 
version_info="lt_cur:lt_rev:lt_age"
AC_SUBST([version_info])
 
AC_PROG_CC
 
PKG_PROG_PKG_CONFIG
 
PKG_CHECK_MODULES([EET], [eet], [have_eet="yes"], [have_eet="no"])
 
AM_PROG_CC_C_O
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT
 
echo
echo
echo "------------------------------------------------------------------------"
echo "$PACKAGE_NAME $PACKAGE_VERSION"
echo "------------------------------------------------------------------------"
echo
echo "Configuration Options Summary:"
echo
echo "  eet..........: ${have_eet}"
echo

You have also other usages of PKG_CHECK_MODULES:

You can check if you dependency library version is greater than a specific version: PKG_CHECK_MODULES([MY_DEP], [eet >= 0.9])
You can check several libraries: PKG_CHECK_MODULES([MY_DEP], [eet freetype])
You can mix the 2 above usages :PKG_CHECK_MODULES([MY_DEP], [eet >= 0.9 freetype])

In those cases, the MY_DEP_CFLAGS variable will have all the -D and -I options for all the libraries passed to PKG_CHECK_MODULES and MY_DEP_LIBS will have all the -L and -l options.

Now, we just have to pass them in the Makefile.am that needs them. MY_DEP_CFLAGS to AM_CPPFLAGS or *_CPPFLAGS, and MY_DEP_LIBS to *_LIBADD (if it's a library) or *_LDADD (if it's a binary). In our example of the foo library:

MAINTAINERCLEANFILES = Makefile.in
   
include_HEADERS = Foo.h
   
lib_LTLIBRARIES = libfoo.la
   
libfoo_la_SOURCES  = foo1.c foo2.c
libfoo_la_CPPFLAGS = -DMY_LIB_DIR=\"$(libdir)\" @MY_DEP_CFLAGS@ @EET_CFLAGS@
libfoo_la_LIBADD = @MY_DEP_LIBS@ @EET_LIBS@
libfoo_la_LDFLAGS = -version-info @version_info@

Windows port

If the library is cross-platform and can be compiled on Windows with the autotools (for example with MSYS and MinGW), then we have to:

make libtool aware of that fact: AC_LIBTOOL_WIN32_DLL, to call before AC_PROG_LIBTOOL
allow libtool to create the dll : -no-undefined to pass to a variable in src/lib/Makefile.am

We can also pass another option to the linker to remove some warnings: --enable-auto-import, but we should do that when we are sure we are on Windows. For that, we just have to check the variable $host_os. We must then add a call of AC_CANONICAL_HOST in configure.ac.

The configure.ac script is then

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
m4_define([lt_cur], [m4_eval([v_maj] + [v_min])])
m4_define([lt_rev], [v_mic])
m4_define([lt_age], [v_min])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
AC_LIBTOOL_WIN32_DLL
define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
AC_PROG_LIBTOOL
 
version_info="lt_cur:lt_rev:lt_age"
AC_SUBST([version_info])
 
AC_CANONICAL_HOST
 
AC_PROG_CC
 
PKG_PROG_PKG_CONFIG
 
PKG_CHECK_MODULES([EET], [eet], [have_eet="yes"], [have_eet="no"])
 
AM_PROG_CC_C_O
 
lt_enable_auto_import=""
case "$host_os" in
   mingw*)
      lt_enable_auto_import="-Wl,--enable-auto-import"
esac
AC_SUBST([lt_enable_auto_import])
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT
 
echo
echo
echo "------------------------------------------------------------------------"
echo "$PACKAGE_NAME $PACKAGE_VERSION"
echo "------------------------------------------------------------------------"
echo
echo "Configuration Options Summary:"
echo
echo "  eet..........: ${have_eet}"
echo

and src/lib/Makefile.am is:

MAINTAINERCLEANFILES = Makefile.in
 
include_HEADERS = Foo.h
 
lib_LTLIBRARIES = libfoo.la
 
libfoo_la_SOURCES  = foo1.c foo2.c
libfoo_la_CPPFLAGS = -DMY_LIB_DIR=\"$(libdir)\" @MY_DEP_CFLAGS@
libfoo_la_LIBADD = @MY_DEP_LIBS@
libfoo_la_LDFLAGS = -no-undefined @lt_enable_auto_import@ -version-info @version_info@

New features and deprecated macros

The construction "AC_INIT AM_INIT_AUTOMAKE([tarname,version])" is obsolete and replaced by "AC_INIT([pkgname], [version]) AM_INIT_AUTOMAKE" instead, since autoconf 2.52 and automake 1.6
INCLUDES is deprecated and replaced by AM_CPPFLAGS since automake 1.6
per-program and per-library _CPPFLAGS since automake 1.7 (autoconf 2.54 required)
LT_INIT interface replaces AC_PROG_LIBTOOL, AC_ENABLE_SHARED, AC_DISABLE_SHARED, AC_ENABLE_STATIC, AC_DISABLE_STATIC, AC_ENABLE_FAST_INSTALL, AC_DISABLE_FAST_INSTALL, AC_LIBTOOL_DLOPEN, AC_LIBTOOL_WIN32_DLL and AC_LIBTOOL_PIC_MODE since libtool 1.9b (actually, since the 2.2 release, in March 2008).

So here is an updated configure.ac:

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
m4_define([lt_cur], [m4_eval([v_maj] + [v_min])])
m4_define([lt_rev], [v_mic])
m4_define([lt_age], [v_min])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
LT_PREREQ([2.2])
LT_INIT([win32-dll])
 
version_info="lt_cur:lt_rev:lt_age"
AC_SUBST([version_info])
 
AC_CANONICAL_HOST
 
AC_PROG_CC
 
PKG_PROG_PKG_CONFIG
 
PKG_CHECK_MODULES([EET], [eet], [have_eet="yes"], [have_eet="no"])
 
AM_PROG_CC_C_O
 
lt_enable_auto_import=""
case "$host_os" in
   mingw*)
      lt_enable_auto_import="-Wl,--enable-auto-import"
esac
AC_SUBST([lt_enable_auto_import])
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT
 
echo
echo
echo "------------------------------------------------------------------------"
echo "$PACKAGE_NAME $PACKAGE_VERSION"
echo "------------------------------------------------------------------------"
echo
echo "Configuration Options Summary:"
echo
echo "  eet..........: ${have_eet}"
echo

M4 macros

Documentation

First, add, in the configure.ac file, the m4 macro EFL_CHECK_DOXYGEN in the program checks part, like that :

EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])

The variable build_doc can be used to show if the documentation is built or not. The configure.ac script is then

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
m4_define([lt_cur], [m4_eval([v_maj] + [v_min])])
m4_define([lt_rev], [v_mic])
m4_define([lt_age], [v_min])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
LT_PREREQ([2.2])
LT_INIT([win32-dll])
 
version_info="lt_cur:lt_rev:lt_age"
AC_SUBST([version_info])
 
AC_CANONICAL_HOST
 
AC_PROG_CC
 
PKG_PROG_PKG_CONFIG
 
EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])
 
PKG_CHECK_MODULES([EET], [eet], [have_eet="yes"], [have_eet="no"])
 
AM_PROG_CC_C_O
 
lt_enable_auto_import=""
case "$host_os" in
   mingw*)
      lt_enable_auto_import="-Wl,--enable-auto-import"
esac
AC_SUBST([lt_enable_auto_import])
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT
 
echo
echo
echo "------------------------------------------------------------------------"
echo "$PACKAGE_NAME $PACKAGE_VERSION"
echo "------------------------------------------------------------------------"
echo
echo "Configuration Options Summary:"
echo
echo "  eet............: ${have_eet}"
echo "  documentation..: ${build_doc}"
echo

Then in the top level Makefile.am file, add doc in the SUBDIRS variable and add later

.PHONY: doc
 
# Documentation
 
doc:
	@echo "entering doc/"
	make -C doc doc

The top level Makefile.am file is then

MAINTAINERCLEANFILES = Makefile.in
 
SUBDIRS = src data doc
.PHONY: doc
 
# Documentation
 
doc:
	@echo "entering doc/"
	make -C doc doc

Finally, create the subdirectory doc and add in it

a Doxyfile file
a Makefile.am file

The doc/Makefile.am file contains:

MAINTAINERCLEANFILES = Makefile.in
 
.PHONY: doc
 
if EFL_BUILD_DOC
 
doc: all
	rm -rf html/ latex/ man/
	$(efl_doxygen)
 
else
 
doc:
	@echo "Documentation not built. Run ./configure --help"
 
endif
 
clean-local:
	@rm -rf html/ latex/ man/
 
EXTRA_DIST = Doxyfile

You can tweak this Makefile.am so that foot, header, css, images can be added to the html output.

Unit tests

Coverage

Benchmark

Layout of a configure.ac script

The autoconf documentation describes how to correctly write a configure.ac file. I have adopted the same way of writing configure.ac files, but i have also added some parts that are not mentioned. Here is what I usually do:

Initialisation of autoconf
initialisation of automake
Initialisation of libtool (with support of Windows)

These 3 parts has been described above. Then:

Default options with respect to the host or not (to enable or disable features according to the host, or other default values used in all the configure script)
Additional options to configure (there, you add --enable or --with options)
Checks for programs (check for compiler, of course, also doxygen with the macro above)
Checks for libraries (most of the time, it's the use of pkg-config, but also with AC_CHECK_LIB, or directly -l***)
Checks for header files (using AC_CHECK_HEADER or AC_CHECK_HEADERS)
Checks for types (if some types are available or not)
Checks for structures (same for structures)
Checks for compiler characteristics (like AC_C_INLINE, AC_C_CONST, AM_PROG_CC_C_O, or compiler stuff like -fno-exception in variables, and preprocessor stuff)
Checks for linker characteristics (adding some specific (Windows ? :) ) linker flags like -Wl,****)
Checks for library functions (like alloca, fnmatch, etc...)
Checks for system services

Once it's done:

Output files (AC_CONFIG_FILES([file...]) and AC_OUTPUT)
Output the needed informations with the 'echo' command

Usually, I always add comments in my configure.ac file, like that:

m4_define([v_maj], [0])
m4_define([v_min], [1])
m4_define([v_mic], [0])
m4_define([project_version], [v_maj.v_min.v_mic])
 
m4_define([lt_cur], [m4_eval([v_maj] + [v_min])])
m4_define([lt_rev], [v_mic])
m4_define([lt_age], [v_min])
 
AC_INIT([my_project], [project_version], [enlightenment-devel@lists.sourceforge.net])
 
AM_INIT_AUTOMAKE([1.6 dist-bzip2])
 
LT_PREREQ([2.2])
LT_INIT([win32-dll])
 
version_info="lt_cur:lt_rev:lt_age"
AC_SUBST([version_info])
 
### Default options
 
AC_CANONICAL_HOST
 
### Additional options to configure
 
### Checks for programs
 
# Compiler
AC_PROG_CC
 
# pkg-config
PKG_PROG_PKG_CONFIG
 
# Documentation
EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])
 
### Checks for libraries
 
PKG_CHECK_MODULES([EET], [eet], [have_eet="yes"], [have_eet="no"])
 
### Checks for header files
 
### Checks for types
 
### Checks for structures
 
### Checks for compiler characteristics
 
AM_PROG_CC_C_O
 
### Checks for linker characteristics
 
lt_enable_auto_import=""
case "$host_os" in
   mingw*)
      lt_enable_auto_import="-Wl,--enable-auto-import"
esac
AC_SUBST([lt_enable_auto_import])
 
### Checks for library functions
 
### Checks for system services
 
AC_CONFIG_FILES([
Makefile
data/Makefile
doc/Makefile
src/Makefile
src/bin/Makefile
src/lib/Makefile
src/tests/Makefile
])
 
AC_OUTPUT
 
echo
echo
echo "------------------------------------------------------------------------"
echo "$PACKAGE_NAME $PACKAGE_VERSION"
echo "------------------------------------------------------------------------"
echo
echo "Configuration Options Summary:"
echo
echo "  eet............: ${have_eet}"
echo "  documentation..: ${build_doc}"
echo

NOTE: I let the comments even if there is no code. It can be useful for other people to update this file.

External links

The Autoconf Manual
The Automake Manual
The libtool Manual

Imported from https://trac.enlightenment.org/e/wiki/AutotoolsIntegration
History:
1 mcalamelli 2009-01-13 14:48:17 WIP
2 mcalamelli 2009-01-13 15:03:55 Done
3 mcalamelli 2009-01-13 15:14:34
4 mcalamelli 2009-01-25 16:59:09 Add H1 title on top
5 vtorri 2009-06-06 23:52:11
6 vtorri 2010-02-10 22:50:43
7 vtorri 2012-03-01 23:56:32
8 vtorri 2012-03-02 00:12:56
9 vtorri 2012-05-23 22:08:43 TOC
10 vtorri 2012-05-24 16:02:30
11 vtorri 2012-05-24 21:44:03
12 vtorri 2012-05-24 21:46:13
13 vtorri 2012-05-24 22:13:32
14 vtorri 2012-05-24 22:18:38

Last Author: beber
Last Edited: Aug 26 2013, 3:02 PM
Projects: None
Subscribers: None

Autotools integrationUpdated 2,153 Days AgoPublicActions