From: Tom Rini <tom_rini@mentor.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] Optionally trade required_utils for -native builds
Date: Fri, 15 Jul 2011 15:03:04 -0700 [thread overview]
Message-ID: <cover.1310758615.git.tom_rini@mentor.com> (raw)
Hey all,
As I said in another thread, today we depend on a few more host utilities
being installed on the host than oe.dev does. This is an attempt to fix
that a bit and improve on the situation at the same time. First up is
adding mercurial-native and then a test to add it to ASSUME_PROVIDED. This
was build tested but I can't spot any hg URIs in the metadata. Next up is
help2man-native. First, I've added the GPLv2 and GPLv3 versions. Second,
I've tested this with qemux86 and core-image-sato and it still all builds
and works as much as it has been for me wrt tests. Finally, in the commit
message I said avoiding perl-native problem and what I'm speaking of is
that since I put help2man-native in with all of the autotools deps, adding
perlnative to the inherits list would bring perl in for everything. We
can punt on this by just not adding target help2man for now.
The following changes since commit e66c2999afa2b3efbce8bb46c89f9db5e15f35c7:
Saul Wold (1):
libx11: ensure nativesdk uses correct DEPENDS and XCB flags
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib trini/add-more-native-recipes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/add-more-native-recipes
Tom Rini (5):
mercurial-native: Add 1.9 version
bitbake.conf, sanity.bbclass: Make mercurial-native optional
help2man-native: Add 1.36.4 (GPLv2) and 1.38.2 (GPLv3)
sanity.bbclass: Add help2man-native to ASSUME_PROVIDED if found
autotools.bbclass: Add help2man-native to the main DEPENDS tree
meta/classes/autotools.bbclass | 4 +-
meta/classes/sanity.bbclass | 10 +++++++-
meta/conf/bitbake.conf | 1 -
.../help2man/help2man-native_1.36.4.bb | 26 ++++++++++++++++++++
.../help2man/help2man-native_1.38.2.bb | 24 ++++++++++++++++++
.../mercurial/mercurial-native_1.9.bb | 24 ++++++++++++++++++
6 files changed, 85 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-devtools/help2man/help2man-native_1.36.4.bb
create mode 100644 meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
create mode 100644 meta/recipes-devtools/mercurial/mercurial-native_1.9.bb
next reply other threads:[~2011-07-15 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 22:03 Tom Rini [this message]
2011-07-15 22:03 ` [PATCH 1/5] mercurial-native: Add 1.9 version Tom Rini
2011-07-15 22:14 ` Khem Raj
2011-07-15 22:22 ` Tom Rini
2011-07-15 22:03 ` [PATCH 2/5] bitbake.conf, sanity.bbclass: Make mercurial-native optional Tom Rini
2011-07-15 22:03 ` [PATCH 3/5] help2man-native: Add 1.36.4 (GPLv2) and 1.38.2 (GPLv3) Tom Rini
2011-07-15 22:24 ` Saul Wold
2011-07-15 22:29 ` Tom Rini
2011-07-15 22:41 ` Saul Wold
2011-07-15 22:47 ` Richard Purdie
2011-07-15 22:48 ` Richard Purdie
2011-07-15 22:53 ` Tom Rini
2011-07-18 22:13 ` Tom Rini
2011-07-19 12:17 ` Phil Blundell
2011-07-19 14:18 ` Tom Rini
2011-07-15 22:03 ` [PATCH 4/5] sanity.bbclass: Add help2man-native to ASSUME_PROVIDED if found Tom Rini
2011-07-15 22:03 ` [PATCH 5/5] autotools.bbclass: Add help2man-native to the main DEPENDS tree Tom Rini
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.1310758615.git.tom_rini@mentor.com \
--to=tom_rini@mentor.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