Re: nested packages

[Ralf Wildenhues]

Hi Bob,

* Bob Rossi wrote on Thu, Apr 13, 2006 at 02:57:48AM CEST:
> On Wed, Apr 12, 2006 at 10:48:15PM +0200, Ralf Wildenhues wrote:
> > * Stepan Kasal wrote on Wed, Apr 12, 2006 at 10:41:58PM CEST:
> > > On Wed, Apr 12, 2006 at 08:39:41AM +0200, Ralf Wildenhues wrote:
> > > > * Bob Rossi wrote on Wed, Apr 12, 2006 at 03:42:51AM CEST:
> > > > > [...] I would like to avoid having to run ./configure
> > > > > twice for the installation of CGDB.
> > 
> > > > Eliminating the second configure run is sometimes possible, but for
> > > 
> > > Ralf, what are you speaking about?  You introduced AC_CONFIG_SUBDIRS,
> > > or eliminated it?
> > 
> > Eliminate AC_CONFIG_SUBDIRS.  Introducing it to run the sub-configure
> > automatically is not so difficult, although many packages have
> > requirements that are not met by the current interface yet.  Getting
> > better though.  :)
> 
> I'm confused now, sorry. Should I use AC_CONFIG_SUBDIRS to configure the
> library or not?

Yes, you should.  AC_CONFIG_SUBDIRS will cause the toplevel configure
script to invoke the sub-configure script, and so both packages should
be ready to be built after just invoking the first.  Invoking `make'
should then build both packages, given that you adjusted SUBDIRS
accordingly in the toplevel Makefile.am.

Before committing to this setup, you should test it extensively, though.
Ideally `make distcheck' should pass.  I'd even go as far and test it
for both the combined packages, and only the inner package along.

I'm sorry for the confusion, I mentioned too many things at once.

> Will the library get installed when 'make install' is done?

Yes, it should.

> I'm not interested in having it installed unless the package is
> being configured on it's own. (Unless the library install dir is the
> same as CGDB's installed dir --prefix=).

OK, that should be fine.

Cheers,
Ralf