[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to configure libtool so that it doesn't run some tests ?
From: |
Ralf Wildenhues |
Subject: |
Re: How to configure libtool so that it doesn't run some tests ? |
Date: |
Mon, 29 Aug 2005 08:50:43 +0200 |
User-agent: |
Mutt/1.4.1i |
* Howard Chu wrote on Mon, Aug 29, 2005 at 08:36:00AM CEST:
> * Patrick PĂ©lissier wrote on Fri, Feb 04, 2005 at 03:03:32PM CET:
> > How to configure libtool so that it doesn't run C++ / Fortran tests if
> > the library is a C library, and so doesn't need a C++ / fortran
> > compiler? The project uses the other autotools and is a C library. I
> > haven't found this in the documentation.
>
> Sorry for dredging up an old question, but recently I was looking for
> the same answer myself. This will probably make the libtool maintainers
> cringe, but I've added this to our configure.in (using libtool 1.5.18)
> to disable the extraneous language tests. (Put this somewhere before the
> AC_PROG_LIBTOOL invocation.)
Sure.
> dnl Disable libtool 1.5 support for languages we don't use
> define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
> define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
> define([AC_LIBTOOL_LANG_GCJ_CONFIG], [:])dnl
>
> It shaves 12000 lines from our configure script and completes faster as
> well (which is a real godsend on some of the ultra slow dev systems we
> port to).
Sure. It should serve as a good workaround.
Libtool 2.0 has this fixed, as already mentioned before. I do not
intend to backport the fix (which doesn't require the user to change
libtool.m4 resp. aclocal.m4) because it is a bit involved.
Cheers,
Ralf