On Thu, Oct 06, 2005 at 04:12:06PM -0400, Chris Shoemaker wrote: > > Looking at autogen.sh raised a bunch more questions than it answered? > > 1) Why do we find every 'configure.in' in the tree to loop over? This > interacts very badly with tools like quilt which copy an unmodified > version of modified files into a hidden directory inside the tree. > I've taken to popping my entire patch stack before running autogen.sh, > but I didn't realize until today that this was our own fault and not > standard behavior of autoconf. Shouldn't we expect to find only one > configure.in? [ I'd never seen that NO-AUTO-GEN trick documented > anywhere. But I can't use it, because quilt manages it's metadata > directories itself. ] >
More on this: If I do a make dist, and then later rerun autogen.sh it will pick up the configure.in from the gnucash-1.99.0 directory. That's also undesirable, no? Any objections to replacing > `find $srcdir -name configure.in -print` with just $srcdir/configure.in? -chris _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
