Re: release thoughts

[Ben Pfaff]

Jason Stover <address@hidden> writes:

> So now we're installing gtk 2.12, but I don't want to install it in
> /usr/lib for fear of clobbering other programs. So it will go into
> /usr/local/lib.
>
> In the past, on every system where I've tested this, pspp will not
> find the newer version of gtk. configure just quits when it sees
> /usr/lib/libgtk* and doesn't bother looking in /usr/local/lib. This is
> going to cause us to lose a lot of users. If they successfully install
> a new version of gtk, then they will quit when pspp fails to find
> it.  So is there an easy way to make sure the configure script
> doesn't just quit when it finds an old version?  It should keep
> searching, at least in /usr/local/lib.

I think that you can specify the necessary C compiler flags and
libraries on the command line directly:
        ./configure GTK_CFLAGS=-I/usr/local/include/gtk 
GTK_LIBS="-L/usr/local/lib -lgtk"

The --help flag to configure shows these as "influential
environment variables".  (Probably, the actual GTK_CFLAGS and
GTK_LIBS will need to be more extensive than that.)

Another, probably easier, option may be to tell pkg-config to
look in /usr/local/lib/pkgconfig (assuming that gtk.pc for GTK+
2.0 can be found there) before /usr/lib/pkgconfig:
        ./configure PKG_CONFIG_PATH=/usr/local/lib/pkgconfig

I am surprised that anyone is still using GTK+ 1.x.
-- 
Only wimps use tape backup: _real_ men just upload their important stuff
on ftp, and let the rest of the world mirror it ;)
        -- Linus Torvalds