How to handle subprojects with autotools?

I have some C++ project build by autotools.

The project uses some libraries, also written by me. Source of libraries are imported to the project as submodules of git. Each library has its own autotools files.

  • Which files generated by Autotools should I keep in version control repository?
  • Bumping version numbers for new releases in associated files (documentation)
  • Displaying from which git commit a binary was compiled
  • Using git for distribution with autotools
  • Compiling workflow with version control
  • Recommended way to use Autoconf Archive macros and other 3rd party macros
  • Say, I have:

    src/<my src files>
    modules/libfoo/
            libbar/
    Makefile.am
    Configure.in
    <other autotools junk>
    

    What I want is to somehow include libraries into main project compilation chain. I guess that just including subdir to Makefile.am is not enough, because some checks can be reformed in configure.am.

  • Installing Git on CentOs
  • Merge old git commit with HEAD at master
  • Difference between git reset commands
  • In Eclipse, xml and xhtml files show unsaved state when switching git branches
  • Add previously ignored directory to Git repository
  • What are git's thin packs?
  • One Solution collect form web for “How to handle subprojects with autotools?”

    You can run the configure scripts in the sub-modules by adding the AC_CONFIG_SUBDIRS command to the top-level configure script. It tells the top-level script to descend into the sub directories and invoke the configure script found there. Then, you can just reference the built libraries from your Makefile.am.

    Read this section of the GNU automake manual.

    Git Baby is a git and github fan, let's start git clone.