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 626107 - glibconfig.h is being disted
glibconfig.h is being disted
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-08-05 13:19 UTC by Allison Karlitskaya (desrt)
Modified: 2010-08-06 20:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allison Karlitskaya (desrt) 2010-08-05 13:19:55 UTC 
Uncovered by bug #625988.

This is enough to ensure that glibconfig.h gets included in the tarball:

DISTCLEANFILES += glibconfig-stamp glibconfig.h
BUILT_SOURCES += glibconfig-stamp
configexecincludedir = $(libdir)/glib-2.0/include
configexecinclude_HEADERS = glibconfig.h



I would have thought that having it on the DISTCLEANFILES list would be enough to ensure that it's not, but that is not the case.

Probably this is related to the weird hack we do to avoid rebuilding the universe every time ./configure is re-run -- it prevents us from having glibconfig.h directly listed in BUILT_SOURCES, so automake probably thinks that it is appropriate to dist it.
Comment 1 Allison Karlitskaya (desrt) 2010-08-05 15:03:30 UTC 
I've figured out how to disable disting it, but it turns out that something things *depend* on glibconfig.h being disted -- for example, gtk-doc only looks in the srcdir for headers to scan....
Comment 2 Allison Karlitskaya (desrt) 2010-08-06 20:41:51 UTC 
Fixed it

And apparently gtk-doc isn't expected to work properly for out-of-tree building anyway, so *shrug*.