Install aclocal portable#
Install aclocal code#

If autoreconf were smarter about autopoint and libtoolize ordering, it mightД®ven be possible to fold much of the bootstrap script nonsense back intoДЄutoreconf, but that's a discussion for another day. With aclocal search and copy rolled into autoconf, it could look the same,ДЄutoconf # m4 dir from AC_CONFIG_MACRO_DIR Here's a minimal modernish bootstrap script: And unfortunate for whoever writes the perl patches, since I didn't do itДЄt least I can help with the design a bit. With a hammer, and make it work, but it would be as unreadable to everyone Me, I'd have written the patches already. If it were in a language that made sense to Painful readings of the Camel and Llama books, I finally gave up trying to I meant unfortunate for me, since after two failed attempts comprising several > efficient, especially for platforms with expensive fork() like Cygwin.ДЄgreed. > easier to use for such 'moderately big' programs.

Install aclocal portable#

> in portable shell scripting would be insane. > I honestly believe having an implementation of autom4te, aclocal or automake > implementation to Perl before I had time to do it :( > I'd have written patches myself long ago, but sadly, Autoconf moved its Where aclocal ends and automake/autoconf begins ) Most likely because the folks that complain can't distinguish between > us to maintain, but doesn't seem a real burden for the users.

> can't be said for automake and autoconf). > Honestly, AFAICS, few people complained about aclocal so far (which sadly > the easier the GBS is to understand and learn.

> about, the less baroque those people will feel that the Autotools are, and the fewer files and tools we have to teach people Tools that still use aclocal can do so harmlessly while it is deprecated,Д«ut in the mean time everyone can begin to move to a more streamlined build Reimplement aclocal as a wrapper to call autoconf

Install aclocal code#

Fold macro search/copy code into autoconf (along with -I argument support)Дў. I think there is no need for such a cumbersome transition. > least a semi-working prototype), and that the community is happy with this > 'replacement' is well underway (that is, designed, agreed upon, and with at > starting even to plan for that move, I'd want to be sure that the intended > it bundled with Automake (this could be done for Automake 1.14). > to move aclocal out into its own git repository, while still distributing > crafted, documented and publicized transition plan. > I think we can't just make it disappear overnight we'd need a carefully But aclocal has existed and been used for so many years now that > files it needs to generate a configure script. > autoconf look for (and if requested, copy into the project tree) all the. > I'd *really* like to see aclocal die as a separate program, and have > was just a stop-gap measure until autoconf could find it's own macros. > I remember many years ago that Tom Tromey (IIRC) stated that aclocal Re: Superseding aclocal? (was: Re: ДљC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal) Re: Superseding aclocal? (was: Re: ДљC_CONFIG_MACRO_DIR Re: Superseding aclocal? (was: Re: ДљC_CONFIG_MACRO_DIR autoconf-patches