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 166226 - glibmmconfig.h not installed
glibmmconfig.h not installed
Status: RESOLVED INVALID
Product: glibmm
Classification: Bindings
Component: build
2.4.x
Other All
: Normal normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on:
Blocks:
 
 
Reported: 2005-02-04 01:55 UTC by Jens Elkner
Modified: 2005-02-07 02:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jens Elkner 2005-02-04 01:55:53 UTC 
Please describe the problem:
make install does not install glibmmconfig.h on make install.
Thus gtkmm can not be build or may use older versions of the file.

Steps to reproduce:
1. Download gtkmm
2. compile
3. make install DESTDIR=/tmp/xxx


Actual results:
install is ok, but /tmp/xxx/include/libglibmm-2.4/glibmmconfig.h is missing

Expected results:
/tmp/xxx/include/libglibmm-2.4/glibmmconfig.h should be there

Does this happen every time?
yes

Other information:
It seems to be the same bug as in libsigc++ install procedure ...
Comment 1 Murray Cumming 2005-02-04 07:25:23 UTC 
It is installed, for instance, in /usr/lib/glibmm-2.4/include/glibmmconfig.h,
because it is platform-specific. All GNOME libraries do this.

pkg-config will report this path. I encourage you to use a mainstream
distribution that installs software via binary packages.
Comment 2 Jens Elkner 2005-02-04 07:34:21 UTC 
Ehhhm, sorry, what?

Includes are as platform specific as libraries are! Stuff, that is not platform
specific should live in share/$something...

So includes in lib dirs are IMHO a polution of the "unwritten?" standards!!!
Please do not start to make *ix a Windooze system!
Comment 3 Murray Cumming 2005-02-05 17:48:44 UTC 
There is nothing whatsoever unusual about this.
Comment 4 Jens Elkner 2005-02-07 02:15:06 UTC 
Well, probably depends on the point of view. I've seen/assembled a lot
of [open source] software (about 400 packages) and the [glib] *mm stuff 
realy breaks out of the "common" scheme. But anyway, I do not wanna make 
this a religios debate.

I 'll just make me a note, that *mm stuff is different and beeing able to
give our students/developers/lug users a hint ...