From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-core@openembedded.org
Subject: Re: [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure.
Date: Wed, 07 Dec 2011 16:40:42 +0000 [thread overview]
Message-ID: <1323276042.30601.42.camel@ted> (raw)
In-Reply-To: <1323273568-31152-1-git-send-email-philip@balister.org>
On Wed, 2011-12-07 at 10:59 -0500, Philip Balister wrote:
> Part of boost needs libraries from icu. Without this, either the build or
> image construction fails. (I forget exactly which)
That is a fairly heavy dependency to add and we're not seeing builds or
images fail due to this being missing as far as I can tell. Do you have
any further information on this?
Cheers,
Richard
> Signed-off-by: Philip Balister <philip@balister.org>
> ---
> meta/recipes-support/boost/boost.inc | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
> index fecdb97..a1499f6 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -6,7 +6,7 @@
> DESCRIPTION = "Free peer-reviewed portable C++ source libraries"
> HOMEPAGE = "http://www.boost.org/"
> SECTION = "libs"
> -DEPENDS = "boost-native zlib"
> +DEPENDS = "boost-native zlib icu"
> DEPENDS_virtclass-native = ""
> LICENSE = "Boost"
>
next prev parent reply other threads:[~2011-12-07 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:59 [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure Philip Balister
2011-12-07 15:59 ` [PATCH 2/2] qt4.inc : Add uic, moc, rcc, and lrelease to tools package Philip Balister
2011-12-07 16:23 ` Koen Kooi
2011-12-07 16:44 ` Philip Balister
2011-12-07 17:31 ` Paul Eggleton
2011-12-07 16:40 ` Richard Purdie [this message]
2011-12-07 16:49 ` [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure Philip Balister
2011-12-07 18:23 ` Richard Purdie
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=1323276042.30601.42.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@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