Bitbucket is a code hosting site with unlimited public and private repositories. We're also free for small teams!



autoconf-lean is a small collection of macros for autoconf and automake which will result in faster configure scripts. It is intended to be used, along with a little bit of common sense, to create configure scripts that do only what they need to, and very little more.

Using lean.m4

Use make to generate lean.m4 from This simply puts the hg or git version information into the file, so you can track what version of autoconf-lean you're using. Put lean.m4 in your project (anywhere will do), then include it in like so:


If anything else is necessary, it will produce warnings during autoreconf.

Making good configure scripts

Using lean.m4 is not the be all end all of making good autoconf scripts. Here is my brief guide:

  1. Use automake. It is better at makefiles than you are.

  2. Avoid libtool if you can.

  3. Do not use autoscan, or if you do, disregard the vast majority of its results. I recommend starting with a template such as the one I've provided in the template directory.

  4. Use AC_CONFIG_AUX_DIR. This simply avoids having all the auxiliary files in your root directory, for cleanliness.

  5. Include lean.m4 after the general initialization and configuration, but before AM_INIT_AUTOMAKE or any tests.

  6. Use autoreconf -i, and add the auxiliary scripts it copies in to your repository so your end users don't have to.

  7. If you feel compelled to create an, this is a correct and modern one:

    exec autoreconf
  8. Most importantly: Only add tests to if you intend to use their results. Checking for the existence of string.h is totally pointless if you don't then use #ifdef HAVE_STRING_H in your code to conditionalize its inclusion. Further, don't add tests if you don't know the proper way to handle the failure case. The most common problem that makes autoconf scripts so slow is completely unused tests.

Recent activity

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.