Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] gtk-doc: Ensure we run gtkdocize else we could see build failures (e.g. evolution-data-server)
Date: Fri, 20 Jul 2012 16:55:46 +0100	[thread overview]
Message-ID: <1342799746.21788.37.camel@ted> (raw)

This is a fix to Ross' series, we need to run gtkdocize in case anything
was built from source control and the appropriate files are missing.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass
index 603b191..8a312f5 100644
--- a/meta/classes/gtk-doc.bbclass
+++ b/meta/classes/gtk-doc.bbclass
@@ -14,3 +14,7 @@ EXTRA_OECONF_append = "\
   --disable-gtk-doc-html \
   --disable-gtk-doc-pdf \
 "
+
+do_configure_prepend () {
+	gtkdocize
+}





             reply	other threads:[~2012-07-20 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 15:55 Richard Purdie [this message]
2012-07-20 19:29 ` [PATCH] gtk-doc: Ensure we run gtkdocize else we could see build failures (e.g. evolution-data-server) Ross Burton
2012-07-22 12:13   ` 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=1342799746.21788.37.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