[Top][All Lists]

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

Re: [PATCH] New language support interface

From: Albert Chin
Subject: Re: [PATCH] New language support interface
Date: Wed, 17 Mar 2004 21:51:24 -0600
User-agent: Mutt/1.4i

On Wed, Mar 17, 2004 at 08:20:09PM +0000, Scott James Remnant wrote:
> Finally, here it is ... the patch you've all been waiting for (really!).
> This removes the AC_LIBTOOL_TAGS macro in favour of a set of LT_INIT
> options and a new LT_LANG macro to select language support.
> The three LT_INIT options are:
>       no-lang         No language support other than C.
>       all-lang        All supported languages
>       auto-lang       Automatically detect required support

Ick. What developer using libtool does _not_ know what languages they
need. Is there every a case where "auto-lang" would not be used?  Why
would a C-based project ever want a non-C-based tag?

Have we decided in favor of two macros to initialize libtool,
LT_INIT([options]), and LT_LANG([tags]) rather than LT_INIT([options],
[tags])? And, because LT_LANG is only of value to an autoconf-based
project and if we can now determine what tags the project uses, how
about we ditch LT_LANG completely. The only reason I ever used
AC_LIBTOOL_TAGS was because the language tags were not inferred

There is the issue of bootstrapping libtool but I think a private
macro should be used for that special-case.

> The options cause LT_LANG to be called for each required language.
> This can be passed either a tag name ("CXX") or an Autoconf-style
> language name ("C++").

Ick. There should be one way to do it, and one way only.

albert chin (address@hidden)

reply via email to

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