I would double-check this personally. I just recently finished a project that asked customers to build an Apache module that depended on autoconf, automake, and libtool. Even though I ran the equivalent of buildconf, the users needed to have all three tools. That may have been because of automake, but I can't be sure and no longer have the project to double check it.
Ryan Quoting Justin Erenkrantz <[EMAIL PROTECTED]>: > --On Thursday, March 4, 2004 10:58 AM -0800 Aaron Bannert <[EMAIL PROTECTED]> > wrote: > > > On Fri, Feb 20, 2004 at 11:16:10AM -0800, Justin Erenkrantz wrote: > >> It'd be trivial to have minotaur run ./buildconf before producing the > >> snapshots. This would lower the barrier of entry on the snapshots: > >> you'd no longer need autoconf, libtool, etc to use those. -- justin > > > > Isn't libtool still needed for the build process? I don't see how running > > ./buildconf would eliminate the libtool dependency. > > Uh, no. When you run buildconf, libtool copies all of its files into the > tree. It's self-contained at that point. -- justin >
