Re: [RFC] Custom tag interface

[Gary V . Vaughan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Scott,

Once again, great work!  I like this patch a lot.

The main issue here is documenting what the user can set with 
LT_TAG_SETVAR,
without forcing them to grub around inside libtool.m4.  I think the 
best way
to do this is to promote the libtool script contents node of 
libtool.texi out
of the maintainers docs, to be part of the official public interface to
libtool.

And if you feel like noting any missing variable docs, that would be 
better
still!

Cheers,
        Gary.

On 17 Mar 2004, at 21:24, Scott James Remnant wrote:
> It gives the user far greater flexibility and control over the tags
> their libtool script will support.  It provides three new macros to do
> this; LT_TAG, LT_TAG_SETVAR and LT_TAG_GETVAR.
>
> LT_TAG creates a copy of a tag, LT_TAG_SETVAR and LT_TAG_GETVAR get and
> set tag variables appropriately.
>
> One example use of these is for package maintainers such as myself; I
> might want a 'libtool' that has C++ support through *both* "libtool 
> g++"
> and "libtool g++".
>
>         LT_TAG([CXX], [BINCXX])
>         LT_TAG_SETVAR([BINCXX], [compiler], ["c++"])
>
>
> This also splits the language and tag relationship somewhat.  Currently
> C++ support is *always* the CXX tag, etc.  This allows the user to
> control that by adding a second argument to LT_LANG.
>
>         LT_LANG(C++, MYCXX)
>
> LT_LANG acts like LT_TAG if the language support is already enabled
> under a different tag name.
>
> Automake can still trace _LT_LANG, the first argument is *always* a
> language name ("C", "CXX", "F77", "GCJ", "RC") the second is a tag
> assigned to it.
- --
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)

iD8DBQFAYWyFFRMICSmD1gYRAni2AJ0a2G8PB5pGand6kz/l4EKIf545IgCgojDd
ZkDVoDoHSv0dND4/Cr9jEpo=
=YnbP
-----END PGP SIGNATURE-----