Bug 113397 - [GTK] [Stable] webkitgtk-2.0.0: GTK_DOC_CHECK not located by gtkdocize
Summary: [GTK] [Stable] webkitgtk-2.0.0: GTK_DOC_CHECK not located by gtkdocize
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: https://bugs.gentoo.org/show_bug.cgi?...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-27 05:34 PDT by Pacho Ramos
Modified: 2014-03-26 07:51 PDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pacho Ramos 2013-03-27 05:34:59 PDT 
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
Comment 1 Martin Robinson 2013-03-27 09:01:11 PDT 
(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.
Comment 2 Pacho Ramos 2013-03-27 11:31:30 PDT 
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...
Comment 3 Martin Robinson 2013-03-28 09:36:12 PDT 
(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.
Comment 4 Pacho Ramos 2013-03-29 02:40:12 PDT 
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 :))
Comment 5 Martin Robinson 2014-03-25 15:21:54 PDT 
We no longer use autotools, so I don't think this an issue any longer.
Comment 6 Pacho Ramos 2014-03-25 23:58:42 PDT 
(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 :/)
Comment 7 Martin Robinson 2014-03-26 07:50:49 PDT 
2.6 will be the first stable release using CMake.
Comment 8 Martin Robinson 2014-03-26 07:51:08 PDT 
I should also mention that the 2.5 unstable series will also use CMake.