* Stepan Kasal wrote on Mon, Apr 03, 2006 at 10:03:16PM CEST:
On Sun, Apr 02, 2006 at 09:28:53PM +0200, Alexandre Duret-Lutz wrote:
SK == Stepan Kasal [EMAIL PROTECTED] writes:
SK But if we release versions with LIBOBJDIR, we will be bounded to
SK support it in future releases, even in case that it will become
SK redundant.
Let's worry when we get there.
Alexandre, you showed me that my proposal needs more thought, thanks.
Let's put it off for now,
Without any desire to discuss possible solutions or issues with
LIBOBJDIR now, I'd still think it good style to let the user know
that this may not be the end of the story, so that at least I
don't feel quite as guilty in case something incompatible will
happen here. Any objections against the patch below (to Autoconf)?
Cheers,
Ralf
* NEWS, doc/autoconf.texi (AC_LIBOBJ vs LIBOBJS): Mark
`LIBOBJDIR' as experimental.
Index: NEWS
===
RCS file: /cvsroot/autoconf/autoconf/NEWS,v
retrieving revision 1.357
diff -u -r1.357 NEWS
--- NEWS5 Apr 2006 22:41:36 - 1.357
+++ NEWS6 Apr 2006 22:06:35 -
@@ -86,6 +86,7 @@
Object names added to these variables are now prefixed with `${LIBOBJDIR}',
as in `${LIBOBJDIR}alloca.o'. LIBOBJDIR is meant to be defined from
`Makefile.in' in case the object files lie in a different directory.
+ The LIBOBJDIR feature is experimental.
** autoreconf
Supports --no-recursive now.
Index: doc/autoconf.texi
===
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.986
diff -u -r1.986 autoconf.texi
--- doc/autoconf.texi 6 Apr 2006 17:51:22 - 1.986
+++ doc/autoconf.texi 6 Apr 2006 22:06:44 -
@@ -16405,6 +16405,7 @@
can be referenced from any @file{Makefile.am}. Even without Automake,
arranging for @code{LIBOBJDIR} to be set correctly will enable
referencing @code{LIBOBJS} and @code{LTLIBOBJS} in another directory.
+The @code{LIBOJBDIR} feature is experimental.
@node AC_FOO_IFELSE vs AC_TRY_FOO
