From: Max Eliaser <max.eliaser@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Suppress Texinfo utilities invoked at build time for -cross & -native recipes
Date: Wed, 14 May 2014 14:35:37 -0700 [thread overview]
Message-ID: <cover.1400103108.git.max.eliaser@intel.com> (raw)
Hello list,
As per discussion with Richard Purdie and others, I'm submitting a patch to
suppress some unnecessary invocations of utilities from the Texinfo suite during
Yocto builds. Specifically, it targets -native and -cross recipes that inherit
texinfo.bbclass.
The Texinfo utilities are suppressed by supplying doppelgänger executables which
understand the same command-line options as the genuine Texinfo utilites, and
which can create blank output files where expected, but which do no actual
processing, formatting, or markup. To see how this is done, look in the
texinfo-dummy-native recipe (under meta/recipes-extended,) added in this patch
series, as well as the modifications to texinfo.bbclass, also in this patch
series.
Suppressing the Texinfo utilities for -native and -cross recipes does provide a
noticable performance gain, as documented in bug 2421. [1] You could make the
case that this patch series still does not completely address bug 2421, as there
are other utilities not from the Texinfo suite (groff, pod2man, etc) which are
not suppressed by these changes.
Target-architecture recipes continue to use the host system's Texinfo utilities
as before, so that dependency is not eliminated by this patch series.
Regards,
-Max Eliaser
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=2421
The following changes since commit 7b78c364b7de901f97cd8dbe56d5e02f545bf3d3:
cleanup-workdir: Fix crosssdk reference after addition of PN (2014-05-05 09:05:42 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib meliaser/texinfo-build
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=meliaser/texinfo-build
Max Eliaser (3):
Allow texinfo, texinfo-native recipes to build w/o host system's
Texinfo utils
Add texinfo-dummy-native recipe w/ scripts to stand in for Texinfo
utils.
native/cross recipes use texinfo-dummy-native; target arch use host's
Texinfo.
meta/classes/texinfo.bbclass | 15 ++-
meta/conf/bitbake.conf | 1 +
.../texinfo-dummy-native/texinfo-dummy-native.bb | 30 +++++
.../texinfo-dummy-native/texinfo-dummy/COPYING | 19 ++++
.../texinfo-dummy-native/texinfo-dummy/template.py | 122 +++++++++++++++++++++
.../texinfo/texinfo/disable-native-tools.patch | 43 --------
.../texinfo/texinfo/use_host_makedoc.patch | 17 ---
meta/recipes-extended/texinfo/texinfo_5.2.bb | 8 +-
8 files changed, 188 insertions(+), 67 deletions(-)
create mode 100644 meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb
create mode 100644 meta/recipes-extended/texinfo-dummy-native/texinfo-dummy/COPYING
create mode 100644 meta/recipes-extended/texinfo-dummy-native/texinfo-dummy/template.py
delete mode 100644 meta/recipes-extended/texinfo/texinfo/disable-native-tools.patch
delete mode 100644 meta/recipes-extended/texinfo/texinfo/use_host_makedoc.patch
--
1.8.3.2
next reply other threads:[~2014-05-14 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 21:35 Max Eliaser [this message]
2014-05-14 21:36 ` [PATCH 1/3] Allow texinfo, texinfo-native recipes to build w/o host system's Texinfo utils Max Eliaser
2014-05-14 21:36 ` [PATCH 2/3] Add texinfo-dummy-native recipe w/ scripts to stand in for " Max Eliaser
2014-05-15 14:29 ` Saul Wold
2014-05-15 17:29 ` Eliaser, MaX
2014-05-14 21:36 ` [PATCH 3/3] native/cross recipes use texinfo-dummy-native; target arch use host's Texinfo Max Eliaser
2014-05-15 21:28 ` [PATCH 0/3] Suppress Texinfo utilities invoked at build time for -cross & -native recipes Saul Wold
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=cover.1400103108.git.max.eliaser@intel.com \
--to=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