After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 327731 - RFE: gtkdocize --force
RFE: gtkdocize --force
Status: RESOLVED NOTABUG
Product: gtk-doc
Classification: Platform
Component: general
1.4
Other Linux
: Normal normal
: ---
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-19 16:55 UTC by Rob Staudinger
Modified: 2007-07-15 11:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rob Staudinger 2006-01-19 16:55:02 UTC 
A --force invocation option would be nice for gtkdocize. If given gtkdocize should not abort on a missing CHECK_GTK_DOC macro in configure.in
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2006-03-21 11:14:53 UTC 
whats the use case for this? Why are you unhappy with using the GTK_DOC_CHECK(X.Y) macro?
Comment 2 Rob Staudinger 2006-05-08 05:37:44 UTC 
E.g. for librsvg i had to default the gtk-doc option to "yes" for fixing "make distcheck". This was done by putting a changed gtk-doc m4 macro into librsvgs configure.in. Of course gtkdocize would fail after that because it wouldn't see the macro in configure.in.
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2007-07-15 09:21:42 UTC 
Wouldn't that be better done by adding this to your Makefile.am?

DISTCHECK_CONFIGURE_FLAGS=--enable-gtk-doc

(This is suggested in the gtkdoc user manual).
Comment 4 Rob Staudinger 2007-07-15 10:13:47 UTC 
(In reply to comment #3)
> Wouldn't that be better done by adding this to your Makefile.am?
> 
> DISTCHECK_CONFIGURE_FLAGS=--enable-gtk-doc
> 
> (This is suggested in the gtkdoc user manual).

If so feel free to close this bug.