[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: 77-gary-diagnose-version-mismatch.patch

From: Alexandre Duret-Lutz
Subject: Re: RFC: 77-gary-diagnose-version-mismatch.patch
Date: Sat, 31 Jan 2004 16:26:35 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

>>> "Scott" == Scott James Remnant <address@hidden> writes:

 Scott> On Fri, 2004-01-30 at 17:54, Gary V. Vaughan wrote:
 >> This patch kind of fell out of me wanting libtool to do automake-like 
 >> version
 >> mismatch checking at runtime, and autoconf-like AC_PREREQ version-minima.
 Scott> Ah, excellent, 

Seconded.  Congrats!


 Scott> I'd like to see us drop AC_LIBTOOL_TAGS too and go for:

 Scott> LT_INIT_LIBTOOL([1.6 C++ disabled-shared])

Note that if AC_LIBTOOL_TAGS is removed, both CVS Autoconf and
CVS Automake need to be changed.  This is not problem, since
none of them has been released yet... but the sooner you settle
on this the better :)

As far as Automake is concerned, AC_LIBTOOL_TAGS is more useful
because that way it can trace the list of supported tags.  With
LT_INIT_LIBTOOL it would get a list of options, with some tags
intermixed.  That could be used too, but it sounds less clean.

 Scott> Basically you get C for free, if you want support for any other
 Scott> languages you have to list the language name in there.  Probably can
 Scott> just steal the language name stuff out of AC_PUSH_LANG, it's friendlier
 Scott> than our tag names, though tag names could be specified too I guess.

 Scott> Using the old AC_PROG_LIBTOOL macro would automatically include all
 Scott> tags.  Could have an all-languages option too?

 >> I've also added an m4_pattern_forbid which means we don't need to keep using
 >> the lame LT_AC_ prefix to pick up unexpanded macros in configure -- we can
 >> migrate to a proper LT_ namespace!  :-)

 Scott> I've never really been able to figure this stuff out,
 Scott> which are valid prefixes and whether you're supposed to
 Scott> use the AC_ namespace outside of Autoconf etc.

It easy: _?(AC|AH|AS|AU|m4)_* macro names are reserved for
Autoconf, and _?AM_* names are reserved for Automake.  Ideally
nobody else should define macros in these namespaces, but
everybody does.
Alexandre Duret-Lutz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]