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.

  • Cause of change from `-arch ppc` to `-arch ppc7400`?
  • Bumping version numbers for new releases in associated files (documentation)
  • Recommended way to use Autoconf Archive macros and other 3rd party macros
  • Using git for distribution with autotools
  • Git diff ignore
  • Compiling workflow with version control
  • 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.

  • Git forced push: how to prevent overriding other user's changes
  • How to push a branch of unknown name to it's remote every time?
  • Should I add deleted files to stage area?
  • How to put repository onto another repository as branch so they have some shared commits?
  • git: programmatically test if index is dirty
  • GIT Rebase Gone Wrong - Possible to Rewrite History to Fix
  • 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.