Skip to contentSkip to conversation

gtk-doc: Ensure we run gtkdocize else we could see build failures (e.g. evolution-data-server)

PATCH In review Richard Purdie 2 participants 3 messages Jul 20, 2012 – Jul 22, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gtk-doc: Ensure we run gtkdocize else we could see build failures (e.g. evolution-data-server)

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.

---

meta/classes/gtk-doc.bbclass +4 -0
index 603b191..8a312f5 100644
@@ -14,3 +14,7 @@ EXTRA_OECONF_append = "\
   --disable-gtk-doc-html \
   --disable-gtk-doc-pdf \
 "
+
+do_configure_prepend () {
+	gtkdocize
+}
#1 lore raw
Quoted 2 lines · Richard Purdie

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.

Good point but I'm curious how the build was succeeding/what broke before this.

Ross

#2 lore raw
Quoted 5 lines · Ross Burton
Quoted 2 lines · Richard Purdie

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.

Good point but I'm curious how the build was succeeding/what broke before this.

Probably you used an existing build which already had the gtk-doc.make file touched and your didn't bump PR. The file therefore hung around. It would only happen on something built from SCM (evolution-data-server is a git recipe).

I'm guessing if you clean eds, it would show up.

Cheers,

Richard