Howdy,
FreeBSD has a strange place to handle gnome 1.0 headers. I've tryed to add a workaround in the configure.in of src/post_modules/GTK but it seems that REALLY_CHECK_HEADER() doesn't take care of new include path.
Is there any good way to handle that ?
/Xavier
In the last episode (Oct 20), Xavier Beaudouin said:
FreeBSD has a strange place to handle gnome 1.0 headers. I've tryed to add a workaround in the configure.in of src/post_modules/GTK but it seems that REALLY_CHECK_HEADER() doesn't take care of new include path.
Is there any good way to handle that ?
Setting GTK_CONFIG=/usr/X11R6/bin/gtk12-config before running configure works for me. The reason it's called gtk12-config is because both gtk-1.1 and gtk-1.2 used the same gtk-config command, so it was impossible to have both installed at once. gtk2 fixed this by using "pkg-config gdk-2.0" (i.e. officially embedding the version name in the package).
yLe Sat, 19 Oct 2002, Dan Nelson a écrit :
In the last episode (Oct 20), Xavier Beaudouin said:
FreeBSD has a strange place to handle gnome 1.0 headers. I've tryed to add a workaround in the configure.in of src/post_modules/GTK but it seems that REALLY_CHECK_HEADER() doesn't take care of new include path.
Is there any good way to handle that ?
Setting GTK_CONFIG=/usr/X11R6/bin/gtk12-config before running configure works for me. The reason it's called gtk12-config is because both gtk-1.1 and gtk-1.2 used the same gtk-config command, so it was impossible to have both installed at once. gtk2 fixed this by using "pkg-config gdk-2.0" (i.e. officially embedding the version name in the package).
Yeah I know that... but the checking part of autoconf in pike sources doesn't "see" the modified path... :)
/Xavier
How did you go about trying to add that workaround then? The configure script uses "gnome-config --cflags ..." to get the CFLAGS to use during the configure checks. Isn't gnome-config broken if it leaves out necessary header paths?
/ Martin Stjernholm, Roxen IS
Previous text:
2002-10-20 00:30: Subject: no gnome.h & freebsd
Howdy,
FreeBSD has a strange place to handle gnome 1.0 headers. I've tryed to add a workaround in the configure.in of src/post_modules/GTK but it seems that REALLY_CHECK_HEADER() doesn't take care of new include path.
Is there any good way to handle that ?
/Xavier
-- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of these mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ Making friends with FreeBSD: Just because the system has panicked doesn`t mean that you should panic too.
/ Brevbäraren
Le Mon, 21 Oct 2002, Martin Stjernholm, Roxen IS @ Pike developers forum a...:
How did you go about trying to add that workaround then? The configure script uses "gnome-config --cflags ..." to get the CFLAGS to use during the configure checks. Isn't gnome-config broken if it leaves out necessary header paths?
kiwi@kiwi:~$ gnome-config --cflags gnome -I/usr/X11R6/include/gnome-1.0 -I/usr/X11R6/include -DNEED_GNOMESUPPORT_H -I/usr/X11R6/lib/gnome-libs/include -I/usr/X11R6/include/gtk12 -I/usr/local/include/glib12 -I/usr/local/include
It seems to give the correct flags, but configure doesn't seems to add it... :/
Previous text:
2002-10-20 00:30: Subject: no gnome.h & freebsd
Howdy,
FreeBSD has a strange place to handle gnome 1.0 headers. I've tryed to add a workaround in the configure.in of src/post_modules/GTK but it seems that REALLY_CHECK_HEADER() doesn't take care of new include path.
Is there any good way to handle that ?
/Xavier
-- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of these mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ Making friends with FreeBSD: Just because the system has panicked doesn`t mean that you should panic too.
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
Dan Nelson -
Martin Stjernholm, Roxen IS ＠ Pike developers forum -
Xavier Beaudouin