On Apr 4, 2000, Tom Tromey <[EMAIL PROTECTED]> wrote:
Michael> - automake forces me to configure libtool for every package.
Michael> I cannot use a configured libtool installed in a base
Michael> package.
> You might be able to make this work somehow, but I don't know it
> offhand.
I *think* this may work (untested):
define([AC_PROG_LIBTOOL],[
LIBTOOL='$(SHELL) (../)+libtool' # as many `../'s as needed :-)
AC_SUBST(LIBTOOL)
])
AC_PROG_LIBTOOL
I think it would be nice if libtool explicitly supported this kind of
source/build-tree architecture. A macro such as
AC_PROG_LIBTOOL_FROM(../..) would do.
However, you won't be able to use `--enable-shared=pkgname' on
packages that configure libtool like this.
Michael> 2. Is there something else that I can read concerning the
Michael> overall design of these tools?
> For automake, no.
Ditto for libtool.
Michael> 3. Would it be possible for me to have someone to pester
Michael> with questions so that I don't violate some design paradigm
Michael> that would prevent my patches from becoming accepted?
> For automake, ask the list. I won't always have time to answer, but
> other people probably will.
Ditto for libtool :-)
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
