Re: gtk+ compile problems...
- From: Joel Becker <jlbec evilplan org>
- To: gtk-devel-list gnome org, nils_barth post harvard edu
- Subject: Re: gtk+ compile problems...
- Date: Fri, 19 May 2000 09:24:19 -0700
On Fri, May 19, 2000 at 11:38:59AM -0400, Nils Barth wrote:
> Aha! Here's the problem.
> I'm not installing Glib 1.3; I have Glib 1.2.7 installed, and I
> compiled but DON'T install Glib 1.3, then configure GTk+ 1.3 with:
> ~/work/software/gtk+$ ./autogen.sh --with-glib=../glib
> and then `make'.
> This worked fine until the beginning of May (about), then died.
GTK+ should (probably) still support that, and tracking that
down I'll leave for others. But...
> ...so I should prolly install Glib 1.3?
> I'm just a little worried about system stability -- can I use
> --prefix and --exec-prefix to put Glib 1.3 somewhere different from
> Glib 1.2?
> How do I do this/what do I need to be aware of so I don't hose my system?
Simply install your development versions of glib/gtk+ in a
separate prefix. Say, /usr/local/test. So, build glib with
--prefix=/usr/local/test. Then, when building GTK+, you only need to
make sure that the 1.3.x glib-config is in the PATH before the 1.2.7
one. eg:
[/usr/build/gtk+]$ PATH=/usr/local/test:$PATH ./configure --prefix=/usr/local/test
As long as the proper glib-config is first in your PATH, the
1.3.x version of GTK+ will link against the 1.3.x glib. You may also
have to update LD_LIBRARY_PATH or ld.so.conf with this new library
directory (/usr/local/test/lib).
To build applications against the 1.3.x gtk+/glib libraries, do
the same thing with your PATH as you configure those applications.
Joel
--
"If women didn't exist, all the money in the world would have
no meaning."
- Aristotle Onassis
jlbec@evilplan.org
http://zenII.uk.linux.org/~jlbec/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]