Mailing-List: contact cvs-help@apr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apr.apache.org
Date: 11 Dec 2001 01:42:10 -0000
Message-ID: <20011211014210.60105.qmail@icarus.apache.org>
From: jerenkrantz@apache.org
To: apr-cvs@apache.org
Subject: cvs commit: apr Makefile.in

jerenkrantz    01/12/10 17:42:10

  Modified:    .        Makefile.in
  Log:
  If we tell libtool what our link dependencies are (by including them when
  we build libapr.la), it will remember the dependencies for us.  So, if a
  third-party (say httpd, flood, SVN, etc.) want to link against libapr.la,
  they don't need to worry about the library dependencies that are currently
  stored in EXTRA_LIBS et al.
  
  This has been tested with libtool-1.4.  Further testing and integration
  needs to be done.  But, this could simplify our build system a bit w.r.t.
  library dependencies.
  
  Revision  Changes    Path
  1.63      +2 -1      apr/Makefile.in
  
  Index: Makefile.in
  ===================================================================
  RCS file: /home/cvs/apr/Makefile.in,v
  retrieving revision 1.62
  retrieving revision 1.63
  diff -u -r1.62 -r1.63
  --- Makefile.in	2001/12/05 20:39:59	1.62
  +++ Makefile.in	2001/12/11 01:42:10	1.63
  @@ -18,6 +18,7 @@
   INSTALL_SUBDIRS=@INSTALL_SUBDIRS@
   
   TARGET_LIB = libapr.la
  +DEPEND_LIBS = @EXTRA_LIBS@ @LIBTOOL_LIBS@
   
   #
   # Rules for building specific targets, starting with 'all' for
  @@ -75,7 +76,7 @@
   
   $(TARGET_LIB):
   	@for i in $(SUBDIRS); do objects="$$objects $$i/*.@so_ext@"; done ; \
  -	    tmpcmd="$(LINK) @lib_target@"; \
  +	    tmpcmd="$(LINK) @lib_target@ $(DEPEND_LIBS)"; \
   	    echo $$tmpcmd; \
   	    $$tmpcmd