libtool-patches
[Top][All Lists]
Advanced

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

Re: [PATCH] support parallel installations


From: Gary V. Vaughan
Subject: Re: [PATCH] support parallel installations
Date: Mon, 15 Nov 2004 12:04:07 +0000
User-agent: Mozilla Thunderbird 0.9 (Macintosh/20041103)

Hi Ralf,

Ralf Wildenhues wrote:
Sorry for late response..

That's okay.  All feedback is good.  :-)

        * configure.ac (APIVERSION): New substituted variable.
        (pkgvdatadir): Ditto.  Versioned data directory.
        (pkgvmacrodir): Ditto.  Versioned aclocal directory.
        (LN): New check for LN command.
        * Makefile.am (aclocal_DATA): Replaced with...
        (pkgvmacro_DATA): ...this.
        (install-data-local): Remove old shared resources.
        (install-exec-hook): Make versioned links to executables.
        (uninstall-hook): Remove versioned files.
        * libltdl/Makefile.am (ltdldatadir): Redefine in terms of
        pkgvdatadir.
        * libltdl/loaders/Makefile.am (ltdldatadir): Ditto.
        * libtoolize.m4sh: Copy macro files from versioned macro directory
        instead of shared aclocal directory.
        * doc/libtool.texi: Document it.
        * NEWS: Updated.

[[...]]

+* In order for this to work, Libtool's aclocal macros are not installed
+  to a shared aclocal dir.  Either change your Makefile.am to use:
+     ACLOCAL_AMFLAGS = -I /usr/share/libtool-1.9g/m4
+  Or change your configure.ac to use:
+     AC_CONFIG_MACRO_DIR([m4])


People might not want to start using a m4 directory now.  Can they use
  AC_CONFIG_MACRO_DIR([.])
as well?

Yes that is fine.  But it will drop all libtool m4 files in $top_srcdir.

Furthermore, I think only recent aclocal's read configure.ac
AC_CONFIG_MACRO_DIR (or there was some associated issue with that).

That's why I offered the ACLOCAL_AMFLAGS option too.  That just copies
the macro files into aclocal.m4.

Since Libtool (at least until yet-to-be version 2.0) wants to support
Automake back to 1.4(?), this change should be tested with older
versions.

Good point.  I'll do that.

Furthermore, people might just not want to change their package merely
for using libtool.  There should be an easy way to get the default
installed libtool.  I'm not sure yet how to accomplish this.

Well, if they want to use libtool-2.0, then they already have to change
their configure.ac to use LT_INIT et. al, and I think it better to put
the parallel install stuff in now so that they only have to change once.

Regards,
Ralf

Thanks for the feedback!

Cheers,
        Gary.
--
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

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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