Hi Bob, * Bob Rossi wrote on Sat, Jan 27, 2007 at 02:32:30PM CET: > > -std_btree_driver_LDADD = -ladt > +std_btree_driver_LDADD = libadt.a > > -std_btree_driver_DEPENDENCIES = $(top_builddir)/various/adt/src > +std_btree_driver_DEPENDENCIES = libadt.a
Hmm. If libadt.a is built in the same directory, then I'd also do the first change, and remove the *_DEPENDENCIES line. That way, dependencies should be computed correctly. See my reply to the other thread for more information. ;-) (The changed *_DEPENDENCIES line looks ok from a casual glance. But why maintain two lines of information if it can be tracked automatically?) (The original *_DEPENDENCIES line looks a bit suspicious. Is that a directory? Depending on a directory isn't portable to all kinds of 'make' implementations.) > If prog_DEPENDENCIES is not supplied, it is computed by Automake. The > automatically-assigned value is the contents of prog_LDADD, with most > configure substitutions, -l, -L, -dlopen and -dlpreopen options removed. > The configure substitutions that are left in are only @LIBOBJS@ and > @ALLOCA@; these are left because it is known that they will not cause an > invalid value for prog_DEPENDENCIES to be generated. > > This makes me think maybe I shouldn't be adding _DEPENDENCIES at all > unless I want to link something in that isn't in LDADD. Is this correct? More or less. Say, you need libfoo built after some other thing is built that isn't a library-to-be-linked-against. For example a file containing a list of exported symbols, to be passed to "libtool --mode=link" as argument to -export-symbols. Cheers, Ralf
