It appears that the existing configure isn't even looking for GTK include
paths at all.  I'm not sure how it ever worked.  So it will only work on
machines that have the gtk, wx and libnotify directories under a directory
that is in the search path.  I won't have time to fix this soon.   Either
somebody else will, or until then you can set your CFLAGS manually.

The reason that we go to pkg-config (or gtk-config) in boinc_gtk.m4 rather
than use gtk-2.0.m4 (which also calls pkg-config) is that, as far as I know,
BOINC doesn't require GTK 2.0, but would compile for wx for GTK+ or wx for
GTK 1.x.  Or wx for plain X11.  Every time we break compatibility, someone
complains.

Eric

2010/5/24 Nicolás Alvarez <[email protected]>

> I just tried compiling BOINC Manager from SVN trunk, on Linux. The
> configure step completed with no errors. When actually building,
> taskbarex.cpp complained gtk/gtk.h and libnotify/notify.h couldn't be
> found.
>
> This is a bug. If the code requires some library's headers to be
> installed, the configure script should check for them and error out if
> they aren't found. If configure gives no errors, then I should be
> pretty sure I already have all the requirements, and running make
> shouldn't give any error caused by missing reqs.
>
> When I went to install those libraries, I found that I already had
> GTK. However, the makefile isn't adding the needed include path, so
> gtk/gtk.h isn't found. gtk.h is in /usr/include/gtk-2.0/gtk/gtk.h, so
> there should be a -I/usr/include/gtk-2.0 passed to the compiler
> (getting the correct path from pkg-config of course).
>
> libnotify requires glib, and it includes it as <glib.h>. I have that
> header in /usr/include/glib-2.0/glib.h, so that's another missing
> include path.
>
> BOINC should probably use the macros in gtk-2.0.m4 instead of trying
> to find GTK by itself using pkg-config...
>
> --
> Nicolas
>
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to