From: Jonathan Callen <jcallen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: multilib@gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] Re: [PATCH multilib-build.eclass] Add multilib_native_use* functions to make ebuild writing easier.
Date: Sat, 19 Apr 2014 15:57:06 -0400 [thread overview]
Message-ID: <5352D512.5050300@gentoo.org> (raw)
In-Reply-To: <1397904806-3079-1-git-send-email-mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
On 04/19/2014 06:53 AM, Michał Górny wrote:
> People are either inlining this or creating local functions for this
> purpose, so it'd be better to have them in the eclass.
>
> RFC: what about '!use'? Should we invert the multilib_build_binaries
> test as well?
> ---
> eclass/multilib-build.eclass | 48 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/eclass/multilib-build.eclass b/eclass/multilib-build.eclass
> index 77e7573..6adfc76 100644
> --- a/eclass/multilib-build.eclass
> +++ b/eclass/multilib-build.eclass
> @@ -462,5 +462,53 @@ multilib_build_binaries() {
> [[ ${COMPLETE_MULTILIB} == yes ]] || multilib_is_native_abi
> }
>
> +# @FUNCTION: multilib_native_use_with
> +# @USAGE: <flag> [<opt-name> [<opt-value>]]
> +# @DESCRIPTION:
> +# Output --with configure option alike use_with if USE <flag> is enabled
> +# and executables are being built (multilib_build_binaries is true).
> +# Otherwise, outputs --without configure option. Arguments are the same
> +# as for use_with in the EAPI.
> +multilib_native_use_with() {
> + if multilib_build_binaries; then
> + use_with "${@}"
> + else
> + echo "--without-${2:-${1}}"
> + fi
> +}
> +
> +# @FUNCTION: multilib_native_use_enable
> +# @USAGE: <flag> [<opt-name> [<opt-value>]]
> +# @DESCRIPTION:
> +# Output --enable configure option alike use_with if USE <flag>
> +# is enabled and executables are being built (multilib_build_binaries
> +# is true). Otherwise, outputs --disable configure option. Arguments are
> +# the same as for use_enable in the EAPI.
> +multilib_native_use_enable() {
> + if multilib_build_binaries; then
> + use_enable "${@}"
> + else
> + echo "--disable-${2:-${1}}"
> + fi
> +}
> +
> +# @FUNCTION: multilib_native_usex
> +# @USAGE: <flag> [<true1> [<false1> [<true2> [<false2>]]]]
> +# @DESCRIPTION:
> +# Output the concatenation of <true1> (or 'yes' if unspecified)
> +# and <true2> if USE <flag> is enabled and executables are being built
> +# (multilib_build_binaries is true). Otherwise, output the concatenation
> +# of <false1> (or 'no' if unspecified) and <false2>. Arguments
> +# are the same as for usex in the EAPI.
> +#
> +# Note: in EAPI 4 you need to inherit eutils to use this function.
> +multilib_native_usex() {
> + if multilib_build_binaries; then
> + usex "${@}"
> + else
> + echo "${3-no}${5}"
> + fi
> +}
> +
> _MULTILIB_BUILD=1
> fi
>
These all look good to me (being one of the offenders mentioned above).
--
Jonathan Callen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
prev parent reply other threads:[~2014-04-19 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 10:53 [gentoo-dev] [PATCH multilib-build.eclass] Add multilib_native_use* functions to make ebuild writing easier Michał Górny
2014-04-19 19:57 ` Jonathan Callen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5352D512.5050300@gentoo.org \
--to=jcallen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=multilib@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox