Re: Re: GLib 2.2.0, GTK+ 2.2.0

Chico Si writes:
 > Thanks, I downloaded fresh zipfiles. But how can I do to install it
 > properly on my system.

Just unzip the (for you) relevant .zip archives into one folder. Add
the (full name of the) "bin" and "lib" folders to your PATH.

As you use MSVC (as you say later), run the command "pkg-config
--msvc-syntax --cflags gtk+-2.0" to see the -I flags that you need to
add to the relevant settings in your MSVC project or makefile. Replace
--cflags with --libs to see what you need to add to the link phase
setting.

 > I format my PC disk and re-install new version of MSVC++ 6.0

 > Now I got the recent zipfiles from Gnu.org for Gimp Windows.

Ummm... you mean gimp.org? And if you are developing software that
uses GTK+, you don't need GIMP.

 > Should I download the bin version or src version or dev-version for
 > GTK+ 2.0.9?

The subject of this thread is GTK+ 2.2.0, not 2.0.9. But anyway, the
"src" zipfiles contain source code. You need that only if you want to
read the source code, or if you intend to make changes to it.

 > How can I install these files (GTK + 2.0.9) to compil my plugins ?

Sigh. Why didn't you say so then right away... GIMP 1.2.x doesn't use
GTK+ 2.0.x (or 2.2.x). GIMP 1.2.x uses GTK+ 1.3.0 (on Windows; on Unix
it uses GTK+ 1.2.x).

Download and unzip the GLib, GTK+ 1.3.0, GLib and GIMP developer
packages. (And add the "bin" and "lib" subfolders to your PATH.) If
your plug-in is a single source file "myplug.c", run the command:

gimptool --msvc-syntax --build myplug.c

 > I can be absurd but I need some help cause I'm very new in C++
 > programs and I'm not very ill-at-ease with Dll notions.

GLib, GTK+ and GIMP are written in C, not C++. If you don't know the
difference, you should.

--tml