On Tue, 31 Jan 2012 11:31:59 +0100, Manuel Ferrero wrote:
I downloaded the all-in-one bundle for Win32, version 2.24.8,
unzipped it and copied it in my disk, then I added the bin path to
PATH variable.
Changing system or user PATH env vars through the control panel
is a *very* bad idea. No single GTK+ version (or anything else
from the GNOME platform stack, like GLib for example) should be
listed in system or user PATH as doing so declares a single
installation
of the platform stack as the "system wide installed" version.
This conflicts badly with our "each app comes with it's own GTK+
runtime environment" philosophy.
Unfortunately, there are "misguided" installers you might encounter
in the wild that seem to insist on doing this anyway (mono's GTK sharp
used to do this, no idea if it still does), making it next to
impossible
to know for sure unless you check the validity of PATH manually.
Now I can compile and run a simple program.
I read on some webpage how to know my GTK version with the following
command line:
pkg-config --variable=gtk_binary_version gtk+-2.0
but the output I get is:
2.10.0
Looks like some other GTK+ installation is also on PATH, before
the entry you added for 2.24.8, resulting in 2.10 getting picked
up instead.
So now I'm confused, do I have the 2.24.8 or the 2.10.0?
You seem to have both.
The most flexible solution is to build yourself a wrapper script
(.bat or .cmd) or in case you use MinGW/MSYS a shell script, that
exports PATH, PKG_CONFIG_PATH and other search paths you need,
the way you want them to be and from that launch the tool you use
to build you program. Such tool might be an MSYS bash session,
eclipse cdt, codeblocks, ...
mvg,
Dieter
_______________________________________________
gtk-list mailing list
gtk-list@xxxxxxxxx
http://mail.gnome.org/mailman/listinfo/gtk-list
