[gentoo-dev] [RFC] autotools support eclass

[Diego 'Flameeyes' Pettenò]

I was wondering last night with az about the handling of autotools.
They not always require to be re-run by scratch, but when you have to run 
aclocal you usually have to run everything after that.
Every ebuild handles them in a different way, some ebuilds run them in a && 
list and then || die, others runs them one-by-one.
Some force updating of support files and some don't.
Some adds code to let them print the status to the screen, some hides the 
actual output and some don't.

Attached there's an "autotools" eclass, it's basically a way to give more 
information to the user while providing an epatch-like die message.
the eauto* calls are directly calls to the original command, without black 
magic, with the only exception of automake that is called with -afc options 
to let it update the support files.

eautoreconf  instead is way different from autoreconf as it simply calls the 
tools one after the other, adding the -I options to eaclocal when requested. 
The sequence is aclocal, autoconf, autoheader, automake, gnuconfig_update and 
libtoolize --copy --force (this seems to be needed quite everytime you run 
aclocal.

Comments?

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)

# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/eclass/eutils.eclass,v 1.194 2005/08/09 
22:40:39 vapier Exp $
#
# Author: Diego Pettenò <[EMAIL PROTECTED]>
#
# This eclass is for handling autotooled software packages that
# needs to regenerate their build scripts.
#
# NB:  If you add anything, please comment it!

inherit eutils gnuconfig

DELEND="sys-devel/automake
        sys-devel/autoconf
        sys-devel/libtool"

# Internal function to run an autotools' tool
autotools_run_tool() {
        local STDERR_TARGET="${T}/$$.out"
        local PATCH_TARGET="${T}/$$.patch"
        local ris

        echo "***** $1 *****" > ${STDERR_TARGET%/*}/$1-${STDERR_TARGET##*/}
        echo >> ${STDERR_TARGET%/*}/$1-${STDERR_TARGET##*/}

        ebegin "Running $1"
        $@ >> ${STDERR_TARGET%/*}/$1-${STDERR_TARGET##*/} 2>&1
        ris=$?
        eend $ris

        if [[ $ris != 0 ]]; then
                echo
                eerror "Failed Running $1 !"
                eerror
                eerror "Include in your bugreport the contents of:"
                eerror
                eerror "  ${STDERR_TARGET%/*}/$1-${STDERR_TARGET##*/}"
                echo
                die "Failed Running $1 !"
        fi
}

# These functions runs the autotools using autotools_run_tool with the
# specified parametes. The name of the tool run is the same of the function
# without e prefix.
# They also force installing the support files for safety.
eaclocal() {
        autotools_run_tool aclocal "$@"
}

eautoheader() {
        autotools_run_tool autoheader "$@"
}

eautoconf() {
        autotools_run_tool autoconf "$@"
}

eautomake() {
        autotools_run_tool automake --add-missing --force-missing --copy "$@"
}

# This function mimes the behavior of autoreconf, but uses the different
# eauto* functions to run the tools. It doesn't accept parameters, but
# the directory with include files can be specified with M4DIR variable.
#
# Note: doesn't run autopoint right now, but runs gnuconfig_update.
eautoreconf() {
        local aclocal_opts

        [[ -n ${M4DIR} ]] && aclocal_opts="-I ${M4DIR}"

        eaclocal $aclocal_opts
        eautoconf
        eautoheader
        eautomake
        gnuconfig_update

        autotools_run_tool libtoolize --copy --force
}

pgpeFZeCcvU6r.pgp
Description: PGP signature