Skip to contentSkip to conversation

thunar: inherit gtk-doc

PATCH New Khem Raj 1 participant 5 messages Jan 14, 2024

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/5 thunar: inherit gtk-doc

Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc then gtkdocize will be called. This means that recipes that don't inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly disable the use of gtkdocize will fail to configure.

Inheriting gtk-doc both solves the configure failure, and allows us to build the API documentation.

[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e

---
 meta-xfce/recipes-xfce/thunar/thunar_4.19.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-xfce/recipes-xfce/thunar/thunar_4.19.0.bb +1 -1
index 02e4ef956a..e4d8b7b4de 100644
@@ -4,7 +4,7 @@ LICENSE = "GPL-2.0-or-later"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 DEPENDS = "libxml-parser-perl-native exo gdk-pixbuf libxfce4ui libnotify xfce4-panel udev"
 
-inherit xfce gobject-introspection features_check mime-xdg perlnative
+inherit xfce gobject-introspection features_check mime-xdg perlnative gtk-doc
 
 # xfce4 depends on libwnck3, gtk+3 and libepoxy need to be built with x11 PACKAGECONFIG.
 # cairo would at least needed to be built with xlib.
Signature · 1 line
2.43.0
author
#1 lore raw

PATCH 2/5 libxklavier: inherit gtk-doc

Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc then gtkdocize will be called. This means that recipes that don't inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly disable the use of gtkdocize will fail to configure.

Inheriting gtk-doc both solves the configure failure, and allows us to build the API documentation.

[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e

---
 meta-gnome/recipes-gnome/libxklavier/libxklavier_5.4.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-gnome/recipes-gnome/libxklavier/libxklavier_5.4.bb +1 -1
index 7955663f26..f52c210ed4 100644
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=6e29c688d912da12b66b73e32b03d812"
 
 DEPENDS = "xkbcomp gtk+ iso-codes libxi libxml2"
 
-inherit autotools pkgconfig gettext gobject-introspection features_check
+inherit autotools pkgconfig gettext gobject-introspection features_check gtk-doc
 
 REQUIRED_DISTRO_FEATURES = "x11"
 
Signature · 1 line
2.43.0
author
#2 lore raw

PATCH 3/5 libwnck: inherit gtk-doc

In reply to Khem Raj

Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc then gtkdocize will be called. This means that recipes that don't inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly disable the use of gtkdocize will fail to configure.

Inheriting gtk-doc both solves the configure failure, and allows us to build the API documentation.

[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e

---
 meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb +1 -1
index 8655affdbb..d7f47002f8 100644
@@ -9,7 +9,7 @@ PACKAGECONFIG ??= "startup-notification"
 PACKAGECONFIG[startup-notification] = "--enable-startup-notification,--disable-startup-notification,startup-notification"
 
 GNOMEBASEBUILDCLASS = "autotools"
-inherit gnomebase gobject-introspection features_check
+inherit gnomebase gobject-introspection features_check gtk-doc
 REQUIRED_DISTRO_FEATURES = "x11"
 
 SRC_URI[archive.md5sum] = "f03e1139296e2a3a92e3b65a3080cd32"
Signature · 1 line
2.43.0
author
#3 lore raw

PATCH 4/5 schroedinger: inherit gtk-doc

In reply to Khem Raj

Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc then gtkdocize will be called. This means that recipes that don't inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly disable the use of gtkdocize will fail to configure.

Inheriting gtk-doc both solves the configure failure, and allows us to build the API documentation.

[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e

---
 .../recipes-multimedia/schroedinger/schroedinger_1.0.11.bb      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-multimedia/recipes-multimedia/schroedinger/schroedinger_1.0.11.bb +1 -1
index c78e008007..e8f6df6348 100644
@@ -19,5 +19,5 @@ SRC_URI[sha256sum] = "1e572a0735b92aca5746c4528f9bebd35aa0ccf8619b22fa2756137a8c
 
 EXTRA_OECONF += "STAGING_DIR=${STAGING_DIR_NATIVE}"
 
-inherit autotools-brokensep pkgconfig
+inherit autotools-brokensep pkgconfig gtk-doc
 
Signature · 1 line
2.43.0
author
#4 lore raw

PATCH 5/5 gst-shark: inherit gtk-doc

In reply to Khem Raj

Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc then gtkdocize will be called. This means that recipes that don't inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly disable the use of gtkdocize will fail to configure.

Inheriting gtk-doc both solves the configure failure, and allows us to build the API documentation.

[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e

---
 .../recipes-multimedia/gstreamer-1.0/gst-shark_0.8.1.bb         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark_0.8.1.bb +1 -1
index 8a839e0d10..dc43bed63b 100644
@@ -31,4 +31,4 @@ FILES:${PN} += "\
     ${libdir}/gstreamer-1.0/libgstsharktracers.la \
 "
 
-inherit autotools gettext pkgconfig
+inherit autotools gettext pkgconfig gtk-doc
Signature · 1 line
2.43.0