jerenkrantz 01/12/10 17:45:45
Modified: . Makefile.in
Log:
If we tell libtool what our link dependencies are (by including them when
we build libaprutil.la), it will remember the dependencies for us. So, if
a third-party (say httpd, flood, SVN, etc.) want to link against
libaprutil.la, they don't need to worry about the library dependencies that
are currently stored in that mess called export_vars.sh.
(This is essentially the same commit just made to APR.)
Revision Changes Path
1.52 +2 -1 apr-util/Makefile.in
Index: Makefile.in
===================================================================
RCS file: /home/cvs/apr-util/Makefile.in,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- Makefile.in 2001/12/05 20:39:16 1.51
+++ Makefile.in 2001/12/11 01:45:44 1.52
@@ -6,6 +6,7 @@
INCLUDES=-I./include -I../include [EMAIL PROTECTED]@/include
TARGET_LIB = libaprutil.la
[EMAIL PROTECTED]@
INSTALL_SUBDIRS = @APR_XML_DIR@
TARGETS = delete-lib $(TARGET_LIB) delete-exports aprutil.exp export_vars.h
@@ -58,7 +59,7 @@
$(TARGET_LIB):
@objects="`find $(SUBDIRS) -name expat -prune -o -name '[EMAIL
PROTECTED]@' -prune -o -name '[EMAIL PROTECTED]@' -print`"; \
- tmpcmd="$(LINK) @lib_target@ @EXTRA_OS_LINK@"; \
+ tmpcmd="$(LINK) @lib_target@ @EXTRA_OS_LINK@ $(DEPEND_LIBS)"; \
echo $$tmpcmd; \
$$tmpcmd
