Bug 113397 – [GTK] [Stable] webkitgtk-2.0.0: GTK_DOC_CHECK not located by gtkdocize

• Status: RESOLVED
• Resolution: INVALID
• Component: WebKitGTK

[Pacho Ramos]

gtkdocize (from gtk-doc-1.18) expects GTK_DOC_CHECK to be present in configure.ac (instead of Source/autotools/FindDependencies.m4), then, currently gtkdocize cannot be run with webkitgtk-2.0.0 sources as it fails with:

gtkdocize: GTK_DOC_CHECK not called in configure.ac


Maybe GTK_DOC_CHECK should be moved back to configure.ac or gtk-doc upstream be notified about this special case :/

Thanks

[Martin Robinson]

(In reply to comment #0)
> gtkdocize (from gtk-doc-1.18) expects GTK_DOC_CHECK to be present in configure.ac (instead of Source/autotools/FindDependencies.m4), then, currently gtkdocize cannot be run with webkitgtk-2.0.0 sources as it fails with:
> 
> gtkdocize: GTK_DOC_CHECK not called in configure.ac
> 
> 
> Maybe GTK_DOC_CHECK should be moved back to configure.ac or gtk-doc upstream be notified about this special case :/

Sounds like a bug in gtkdocize. :) Out of curiosity, why are you running gtkdocize on a project that already has gtkdoc support? Our support is a bit unusual, because we don't really use the builtin autotools support to the full extent.

[Pacho Ramos]

Well, under Gentoo we get it run (with other tools like intltoolize, gettext...) before aclocal and autoreconf when we need to patch something in Makefile.am, configure.ac...

[Martin Robinson]

(In reply to comment #2)
> Well, under Gentoo we get it run (with other tools like intltoolize, gettext...) before aclocal and autoreconf when we need to patch something in Makefile.am, configure.ac...

Do you know why this is the case? I don't understand what can be gained by running gtkdocize in the WebKit source tree.

[Pacho Ramos]

Well, we are discussing downstream to make this optional:
https://bugs.gentoo.org/show_bug.cgi?id=459978

but, anyway, I thought you should be aware of the problem (if you opt for not allowing to run gtkdocize, ok :))

[Martin Robinson]

We no longer use autotools, so I don't think this an issue any longer.

[Pacho Ramos]

(In reply to comment #5)
> We no longer use autotools, so I don't think this an issue any longer.

What will be the first version not using autotools? (looks like 2.4.0 still does :/)

[Martin Robinson]

2.6 will be the first stable release using CMake.

[Martin Robinson]

I should also mention that the 2.5 unstable series will also use CMake.