From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libxpm-native: add dependency on gettext-native
Date: Mon, 20 Aug 2012 14:16:54 -0700 [thread overview]
Message-ID: <5032A946.1000301@linux.intel.com> (raw)
In-Reply-To: <1343959047-24613-2-git-send-email-sen.zhang@windriver.com>
On 08/02/2012 06:57 PM, Jesse Zhang wrote:
> libxpm needs xgettext to build po files. Add explicit dependency on
> gettext-native.
>
> Signed-off-by: Jesse Zhang <sen.zhang@windriver.com>
> ---
> meta/recipes-graphics/xorg-lib/libxpm_3.5.10.bb | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-graphics/xorg-lib/libxpm_3.5.10.bb b/meta/recipes-graphics/xorg-lib/libxpm_3.5.10.bb
> index 9eaa212..6830216 100644
> --- a/meta/recipes-graphics/xorg-lib/libxpm_3.5.10.bb
> +++ b/meta/recipes-graphics/xorg-lib/libxpm_3.5.10.bb
> @@ -10,7 +10,8 @@ protocol."
> LICENSE = "BSD"
> LIC_FILES_CHKSUM = "file://COPYING;md5=3e07763d16963c3af12db271a31abaa5"
> DEPENDS += "libxext libsm libxt"
> -PR = "r0"
> +DEPENDS_virtclass-native = "gettext-native"
Is there a reason you don't do an inherit gettext here to ensure other
bits are set? Also for the native, you maybe able to use the
gettext-minimal-native if there is reason you can't use the inherit.
Sau!
> +PR = "r1"
> PE = "1"
>
> XORG_PN = "libXpm"
>
next prev parent reply other threads:[~2012-08-20 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 1:57 [PATCH] libxpm-native: add dependency on gettext-native Jesse Zhang
2012-08-03 1:57 ` Jesse Zhang
2012-08-20 21:16 ` Saul Wold [this message]
2012-08-21 1:35 ` Jesse Zhang
2012-08-21 15:40 ` Saul Wold
2012-08-24 4:28 ` [PATCH v2 0/1] libxpm: inherit gettext Jesse Zhang
2012-08-24 4:28 ` [PATCH 1/1] " Jesse Zhang
2012-08-16 17:51 ` [PATCH] libxpm-native: add dependency on gettext-native Saul Wold
2012-08-20 19:09 ` Mark Hatle
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=5032A946.1000301@linux.intel.com \
--to=sgw@linux.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