Hi Baurzhan, * Baurzhan Ismagulov wrote on Tue, Jun 28, 2005 at 04:59:36PM CEST: > On Tue, Jun 07, 2005 at 04:16:26PM +0200, Ralf Wildenhues wrote: > > > > d1, d2, l1, l2, src1, src2 are existing projects with Makefile or > > > configure.ac / Makefile.am. I want to leave them as they are and write a > > > Makefile that would build them in the necessary order according to the > > > dependencies. > > > > > > So, how can I specify the build dependencies? > > > > Put > > AC_CONFIG_SUBDIRS([d1 d2 l1 l2 src1 src2]) > > in toplevel configure.ac and > > SUBDIRS = d1 d2 l1 l2 src1 src2 > > in toplevel Makefile.am, in the order in which you want them configured > > resp. built. > > I've tried to implement that. I've put the following line in my topmost > configure.ac: > > AC_CONFIG_SUBDIRS(lib/l1 src1) > > configure runs configure in lib/l1 and src1. However, src1/configure > tries to link against lib/l1/libl1.a and fails since it can't find it.
Hmm. I don't know whether AC_CONFIG_SUBDIRS can give you the flexibility you want here. If you unconditionally build both packages, there is no need to check for libl1 during src1/configure. I agree that this limits flexibility, but don't know of anything better off my head (maybe someone else can suggest a better way). > So I need to have lib/l1 built before I can configure src1. > The only solution that I can think of is to use configure-stamp, > make-stamp and introduce custom dependencies between them. Or just take the existence of the library for granted: you know that it will be built. Regards, Ralf