From: Ben Gamari <bgamari.foss@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Using native package build tree when building target package
Date: Mon, 17 Jan 2011 18:21:15 -0500 [thread overview]
Message-ID: <87hbd7ruac.fsf@gmail.com> (raw)
Today I've been looking at the icu package, which is quite out-of-date
in the repository. Unfortunately, it seems that the latest version (4.6)
requires that the absolute path to a source tree built for the host be
passed to configure.
Does anyone have any clever ideas concerning how this might be
accomplished? Does this mean that we'll need to merge the icu and
icu-native recipes? My bitbake-fu is pretty weak, so I'd appreciate any
help. Thanks!
- Ben
reply other threads:[~2011-01-17 23:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87hbd7ruac.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.