[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How to approach nested autoconf package configuration

From: Germán Diago Gómez
Subject: How to approach nested autoconf package configuration
Date: Fri, 01 Jun 2012 22:42:46 +0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

Hello everyone,

I would like to ask a question I couldn't solve about autotools nested packages.

I have a project with subdirectories that use autoconf as well. The (simplified) structure is this one:


Actually they are separate projects (separate git repos) and I created a superproject (another git repo) that holds both. The problem I find is that configure checks for ProjectBinary should find LibProject. For that I want to use PKG_CHECK_MODULES([DEPS], [LibProject]) inside ProjectBinary/ but since ProjectBinary runs configure before LibProject is compiled and installed, ProjectBinary cannot find LibProject module. I added an option to disable PKG_CHECK_MODULES and add the library to the linker manually in, but it looks like cheating to me. So my question is:

- Is there a well-known/standard way to avoid this? One idea I have (if possible) would be compiling and installing immediately after configuring LibProject, and, after this, go into ProjectBinary. But autoconf first executes all checks for all packages and later compiles and installs (at least by default).


Germán Diago Gómez

reply via email to

[Prev in Thread] Current Thread [Next in Thread]