Alexandre Thanks for the info. I really appreciate it. What is the easiest way then to tell system to go to a different directory to build a dependency if it is not built yet??
By the way, if you don't mind me asking, what is the point of _DEPENDENCIES when you can just add library to _LDADD and Autotools will update dependency list automatically from that??? Chris > -------- Original Message -------- > Subject: Re: Problems getting dependencies compiled before > executable.... > From: "Alexandre Duret-Lutz" <[EMAIL PROTECTED]> > Date: Sat, June 14, 2003 12:19 pm > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] > > >>> "Chris" == Chris Seberino <[EMAIL PROTECTED]> writes: > > [...] > > Chris> If a dependency of a target is not built, then Makefile > Chris> should build the dependency first. That is not what > Chris> is happening here. Why can't Makefile go to right > Chris> directory to build the dependency??? > > [...] > > Because the rules to build this dependency are in the > subdirectory not in the current one. See > http://www.tip.net.au/~millerp/rmch/recu-make-cons-harm.html > for some background. > > You can tell Automake you want the subdirectory built *after* > the current one by changing src/Makefile.am's SUBDIRS definition > to > > SUBDIRS = . exec > > Alternatively, you can merge src/exec/Makefile.am into > src/Makefiles.am. It's ok to write things like > > noinst_LIBRARIES = libfoo.a > libfoo_a_SOURCES = foo.c > bin_PROGRAMS = exec/main > exec_main_SOURCES = exec/main.c > exec_main_LDADD = libfoo.a > > -- > Alexandre Duret-Lutz