From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gtk-doc.bbclass: unbreak dependency-chain for native recipes
Date: Thu, 26 Jul 2012 16:59:38 +0100 [thread overview]
Message-ID: <1343318378.7600.9.camel@ted> (raw)
In-Reply-To: <1343315761-6314-1-git-send-email-schnitzeltony@googlemail.com>
On Thu, 2012-07-26 at 17:16 +0200, Andreas Müller wrote:
> Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
> ---
> meta/classes/gtk-doc.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass
> index 8a312f5..be10c75 100644
> --- a/meta/classes/gtk-doc.bbclass
> +++ b/meta/classes/gtk-doc.bbclass
> @@ -7,7 +7,7 @@
> # packages up any existing documentation (so from tarball builds).
>
> DEPENDS_append = " gtk-doc-stub-native"
> -DEPENDS_virtclass-native_append = " gtk-doc-stub-native"
> +DEPENDS_append_virtclass-native = " gtk-doc-stub-native"
>
> EXTRA_OECONF_append = "\
> --disable-gtk-doc \
What happens if we simply remove this line entirely?
Do we have any recipes setting DEPENDS_virtclass-native which also use
this class? If so, we might end up just hardcoding things...
Cheers,
Richard
prev parent reply other threads:[~2012-07-26 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 15:16 [PATCH] gtk-doc.bbclass: unbreak dependency-chain for native recipes Andreas Müller
2012-07-26 15:19 ` Burton, Ross
2012-07-26 15:35 ` Andreas Müller
2012-07-26 15:49 ` Chris Larson
2012-07-26 15:59 ` Richard Purdie [this message]
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=1343318378.7600.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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