You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@apr.apache.org by ji...@locus.apache.org on 2000/11/30 00:11:27 UTC

cvs commit: apr apr_common.m4

jim         00/11/29 15:11:24

  Modified:    .        apr_common.m4
  Log:
  Explain the "magic". Might be moot if we hard-code the logic
  in anyway, but what the hell. :)
  
  Revision  Changes    Path
  1.9       +10 -1     apr/apr_common.m4
  
  Index: apr_common.m4
  ===================================================================
  RCS file: /home/cvs/apr/apr_common.m4,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- apr_common.m4	2000/11/28 21:31:52	1.8
  +++ apr_common.m4	2000/11/29 23:11:21	1.9
  @@ -229,7 +229,16 @@
   dnl  Handle the use of EXTRA_* variables.
   dnl  Basically, EXTRA_* vars are added to the
   dnl  current settings of their "parents". We
  -dnl  can expand as needed. This is ugly
  +dnl  can expand as needed for additional
  +dnl  EXTRA_* variables by adding them to the
  +dnl  "for i in..." line.
  +dnl
  +dnl  To handle recursive configures, the 1st time
  +dnl  through we need to null out EXTRA_* and then
  +dnl  export the lot of them, since we want/need
  +dnl  them to exist in the sub-configures' environment.
  +dnl  The nasty eval's allow us to use the 'for'
  +dnl  construct and save some lines of code.
   dnl
   AC_DEFUN(APR_DOEXTRA, [
     for i in CFLAGS LDFLAGS LIBS