I've tried to compile a simple Gtk window over and over but have been unable too. I inculde the full directory to gtk.h (/usr/include/gtk-1.2/gtk/gtk.h) in the #include statement, but compilation never works. It prints a long list of errors, claiming that a large number of headers do not exist, when they do, right in the same directory as gtk.h. I have no idea what the problem is or what to do about it.

I'm not veryy familiar with slackware, but IRCC slackware does not ahve a seperate package for development (header) files for each library like most other distro's do (is this correct?).

If you have the GTK libs package installed, just:And compile with:

Hi -

Hko is absolutely correct. A couple of additional notes:

1. If your "gtk.h" header is in "/usr/include/gtk-1.2/gtk/gtk.h", then:

a) Your source file must read "#include <gtk/gtk.h>"
... and ...
b) Your "-I" compile switch must point to the gtk/ directory and not the gtk.h header:
"-I /usr/include/gtk-1.2"

2. You should be able to use "gtk-config --cflags" to get the correct GTK+ compile
flags ... and "gtk-config --libs" for the GTK+ link flags ... and "glib-config --cflags" for
the Glib compile flags ... etc etc

Just FYI, in GTK+2 all the individual "*-config" scripts have been replaced with
a single "pkg-config" script.

If you prefer, you can also just hard-code the correct flags into your makefile. In
some cases, this might actually be easier and more effective than debugging
the *config" scripts.

3. You might have different GTK+ headers in different directories. For example, on my
SuSE system, I have some of the GTK+ headers in /usr/include ... and others in
/usr/lib/gtk*/include. So you might need multiple different "-I" switches (and, when
you're past the compile errors, multiple different "-L" link siwtches).

4. Look at the *first* compile error, at the top of the errors. That will be the most important
to understand the actual problem.

'Hope that helps .. PSM

vi gtk.h and find all .h file included and confirm their exists
you may find /usr/include/xx/xx1.h indeed appears in /usr/include/xx1.2/xx1.h
then copy it to right place

Uh - no.

You practically *never* want to copy a system header file "someplace else".

Using "pkg-config" is the best way to go, if at all possible. Using as many "-I" include directory commands to gcc is your best alternative.

I certainly agree with paulsm4.
The headers are in the right place. If it's not, your installation is broken and you should fix that instead.