Message ID | 20240114072014.601505-3-raj.khem@gmail.com |
---|---|
State | Accepted |
Headers | show |
Series | [meta-xfce,1/5] thunar: inherit gtk-doc | expand |
diff --git a/meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb b/meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb index 8655affdbb..d7f47002f8 100644 --- a/meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb +++ b/meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb @@ -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"
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 Signed-off-by: Khem Raj <raj.khem@gmail.com> --- meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)