Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Max Eliaser <max.eliaser@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] texinfo.bbclass: native/cross uses dummy texinfo; target uses host's Texinfo.
Date: Fri, 13 Jun 2014 12:32:56 +0100	[thread overview]
Message-ID: <1402659176.12440.478.camel@ted> (raw)
In-Reply-To: <4b7de930ed0850b747248daf99495d5779d7156d.1402431641.git.max.eliaser@intel.com>

On Tue, 2014-06-10 at 13:24 -0700, Max Eliaser wrote:
> To unpack that to more than a single line: -native and -cross recipes are made
> to use the dummy Texinfo utilities provided by texinfo-dummy-native if they
> invoke those utilities at build time. The target-architecture (cross-compiled)
> recipes still use the genuine Texinfo utilites. Right now, they still use
> the host system's Texinfo utilities, but could be made to use the
> texinfo-native recipe we already ship with some config file changes.
> 
> Signed-off-by: Max Eliaser <max.eliaser@intel.com>
> ---
>  meta/classes/texinfo.bbclass | 15 ++++++++++++++-
>  meta/conf/bitbake.conf       |  1 +
>  2 files changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/texinfo.bbclass b/meta/classes/texinfo.bbclass
> index 60cba0f..92efbcc 100644
> --- a/meta/classes/texinfo.bbclass
> +++ b/meta/classes/texinfo.bbclass
> @@ -1,2 +1,15 @@
>  # This class is inherited by recipes whose upstream packages invoke the
> -# texinfo utilities at build-time. This class currently does nothing.
> +# texinfo utilities at build-time. Native and cross recipes are made to use the
> +# dummy scripts provided by texinfo-dummy-native, for improved performance. 
> +# Target architecture recipes use the genuine Texinfo utilities. By default, 
> +# they use the Texinfo utilities on the host system. If you want to use the
> +# Texinfo recipe shipped with yoco, you can remove texinfo-native from 
> +# ASSUME_PROVIDED and makeinfo from SANITY_REQUIRED_UTILITIES.
> +
> +TEXDEP = "texinfo-native"
> +TEXDEP_class-native = "texinfo-dummy-native"
> +TEXDEP_class-cross = "texinfo-dummy-native"
> +

I took this patch but I noticed we should have a class-crosssdk in there
too. Its not a big issue, just a completeness thing.

Cheers,

Richard



  reply	other threads:[~2014-06-13 11:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 20:24 [PATCH 0/3] Suppress Texinfo utilities invoked at build time for -cross & native recipes (revised) Max Eliaser
2014-06-10 20:24 ` [PATCH 1/3] texinfo: Use texinfo-replacement-native as an alias for texinfo-native Max Eliaser
2014-06-10 20:24 ` [PATCH 2/3] texinfo-dummy-native: Create recipe w/ scripts to stand in for Texinfo utils Max Eliaser
2014-06-10 20:24 ` [PATCH 3/3] texinfo.bbclass: native/cross uses dummy texinfo; target uses host's Texinfo Max Eliaser
2014-06-13 11:32   ` Richard Purdie [this message]
2014-06-10 21:06 ` [PATCH 0/3] Suppress Texinfo utilities invoked at build time for -cross & native recipes (revised) Mark Hatle
2014-06-10 21:52   ` Eliaser, MaX

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=1402659176.12440.478.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=max.eliaser@intel.com \
    --cc=openembedded-core@lists.openembedded.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