Files
gentoo/eclass/waf-utils.eclass
Robin H. Johnson 56bd759df1 proj/gentoo: Initial commit
This commit represents a new era for Gentoo:
Storing the gentoo-x86 tree in Git, as converted from CVS.

This commit is the start of the NEW history.
Any historical data is intended to be grafted onto this point.

Creation process:
1. Take final CVS checkout snapshot
2. Remove ALL ChangeLog* files
3. Transform all Manifests to thin
4. Remove empty Manifests
5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$
5.1. Do not touch files with -kb/-ko keyword flags.

Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests
X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project
X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration
X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn
X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts
X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration
X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging
X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
2015-08-08 17:38:18 -07:00

130 lines
4.6 KiB
Bash

# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
# @ECLASS: waf-utils.eclass
# @MAINTAINER:
# maintainer-needed@gentoo.org
# @AUTHOR:
# Original Author: Gilles Dartiguelongue <eva@gentoo.org>
# Various improvements based on cmake-utils.eclass: Tomáš Chvátal <scarabeus@gentoo.org>
# Proper prefix support: Jonathan Callen <jcallen@gentoo.org>
# @BLURB: common ebuild functions for waf-based packages
# @DESCRIPTION:
# The waf-utils eclass contains functions that make creating ebuild for
# waf-based packages much easier.
# Its main features are support of common portage default settings.
inherit eutils multilib toolchain-funcs multiprocessing
case ${EAPI:-0} in
4|5) EXPORT_FUNCTIONS src_configure src_compile src_install ;;
*) die "EAPI=${EAPI} is not supported" ;;
esac
# Python with threads is required to run waf. We do not know which python slot
# is being used as the system interpreter, so we are forced to block all
# slots that have USE=-threads.
DEPEND="${DEPEND}
dev-lang/python
!dev-lang/python[-threads]"
# @ECLASS-VARIABLE: WAF_VERBOSE
# @DESCRIPTION:
# Set to OFF to disable verbose messages during compilation
# this is _not_ meant to be set in ebuilds
: ${WAF_VERBOSE:=ON}
# @FUNCTION: waf-utils_src_configure
# @DESCRIPTION:
# General function for configuring with waf.
waf-utils_src_configure() {
debug-print-function ${FUNCNAME} "$@"
if [[ ! ${_PYTHON_ANY_R1} && ! ${_PYTHON_SINGLE_R1} && ! ${_PYTHON_R1} ]]; then
eqawarn "Using waf-utils.eclass without any python-r1 suite eclass is not supported"
eqawarn "and will be banned on 2015-01-24. Please make sure to configure and inherit"
eqawarn "appropriate -r1 eclass. For more information and examples, please see:"
eqawarn " https://wiki.gentoo.org/wiki/Project:Python/waf-utils_integration"
else
if [[ ! ${EPYTHON} ]]; then
eqawarn "EPYTHON is unset while calling waf-utils. This most likely means that"
eqawarn "the ebuild did not call the appropriate eclass function before calling waf."
if [[ ${_PYTHON_ANY_R1} ]]; then
eqawarn "Please ensure that python-any-r1_pkg_setup is called in pkg_setup()."
elif [[ ${_PYTHON_SINGLE_R1} ]]; then
eqawarn "Please ensure that python-single-r1_pkg_setup is called in pkg_setup()."
else # python-r1
eqawarn "Please ensure that python_setup is called before waf-utils_src_configure(),"
eqawarn "or that the latter is used within python_foreach_impl as appropriate."
fi
eqawarn
fi
if [[ ${PYTHON_REQ_USE} != *threads* ]]; then
eqawarn "Waf requires threading support in Python. To accomodate this requirement,"
eqawarn "please add 'threads(+)' to PYTHON_REQ_USE variable (above inherit line)."
eqawarn "For more information and examples, please see:"
eqawarn " https://wiki.gentoo.org/wiki/Project:Python/waf-utils_integration"
fi
fi
local libdir=""
# @ECLASS-VARIABLE: WAF_BINARY
# @DESCRIPTION:
# Eclass can use different waf executable. Usually it is located in "${S}/waf".
: ${WAF_BINARY:="${S}/waf"}
# @ECLASS-VARIABLE: NO_WAF_LIBDIR
# @DEFAULT_UNSET
# @DESCRIPTION:
# Variable specifying that you don't want to set the libdir for waf script.
# Some scripts does not allow setting it at all and die if they find it.
[[ -z ${NO_WAF_LIBDIR} ]] && libdir="--libdir=${EPREFIX}/usr/$(get_libdir)"
tc-export AR CC CPP CXX RANLIB
echo "CCFLAGS=\"${CFLAGS}\" LINKFLAGS=\"${CFLAGS} ${LDFLAGS}\" \"${WAF_BINARY}\" --prefix=${EPREFIX}/usr ${libdir} $@ configure"
# This condition is required because waf takes even whitespace as function
# calls, awesome isn't it?
if [[ -z ${NO_WAF_LIBDIR} ]]; then
CCFLAGS="${CFLAGS}" LINKFLAGS="${CFLAGS} ${LDFLAGS}" "${WAF_BINARY}" \
"--prefix=${EPREFIX}/usr" \
"${libdir}" \
"$@" \
configure || die "configure failed"
else
CCFLAGS="${CFLAGS}" LINKFLAGS="${CFLAGS} ${LDFLAGS}" "${WAF_BINARY}" \
"--prefix=${EPREFIX}/usr" \
"$@" \
configure || die "configure failed"
fi
}
# @FUNCTION: waf-utils_src_compile
# @DESCRIPTION:
# General function for compiling with waf.
waf-utils_src_compile() {
debug-print-function ${FUNCNAME} "$@"
local _mywafconfig
[[ "${WAF_VERBOSE}" ]] && _mywafconfig="--verbose"
local jobs="--jobs=$(makeopts_jobs)"
echo "\"${WAF_BINARY}\" build ${_mywafconfig} ${jobs}"
"${WAF_BINARY}" ${_mywafconfig} ${jobs} || die "build failed"
}
# @FUNCTION: waf-utils_src_install
# @DESCRIPTION:
# Function for installing the package.
waf-utils_src_install() {
debug-print-function ${FUNCNAME} "$@"
echo "\"${WAF_BINARY}\" --destdir=\"${D}\" install"
"${WAF_BINARY}" --destdir="${D}" install || die "Make install failed"
# Manual document installation
einstalldocs
}