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 52458 - .c file dependency for docs
.c file dependency for docs
Status: RESOLVED FIXED
Product: gtk-doc
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks: 99283
 
 
Reported: 2001-03-23 23:40 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Havoc Pennington 2001-03-23 23:40:30 UTC 
Should have a dependency on the .c files and redo the scan step in that case.
Comment 1 Sven Neumann 2002-03-05 16:08:52 UTC 
There is a dependency on .c files for the sgml target (C_FILES_GLOB).
IMO that should be sufficient.
Comment 2 Owen Taylor 2002-03-05 20:55:28 UTC 
Its' actually not sufficient because new properties, say, 
would have an effect at the scan stage not the SGML stage.
Comment 3 Owen Taylor 2002-03-20 20:45:10 UTC 
Moving docs bugs from 2.0.1 => 2.0.2
Comment 4 Matthias Clasen 2002-04-05 13:34:01 UTC 
Move open bugs from milestones 2.0.[012] -- > 2.0.3, since 2.0.2 is already out.
Comment 5 Matthias Clasen 2002-11-22 09:52:02 UTC 
Is this actually a gtk-doc bug ?
Comment 6 Matthias Clasen 2002-11-26 10:17:32 UTC 
I think it is. We should fix the example / "standard" gtk-doc Makefile.
Comment 7 Damon Chaplin 2004-02-15 16:13:27 UTC 
So we just need to change:

scan-build.stamp: $(HFILE_GLOB)

to:

scan-build.stamp: $(HFILE_GLOB) $(CFILE_GLOB)

Right? That seems OK to me. It means scanning will happen more often,
but shouldn't matter since people rarely run make in the toplevel dir.
Comment 8 Damon Chaplin 2004-10-14 19:00:27 UTC 
I've committed the above change, and it now rescans if a .c file changes.