Thanks so much for your response 95se (windows version is your name?)
The included makefile, Makefile.am, has this as its contents:
#Build the executable, but don't install it.
noinst_PROGRAMS = helloworld
helloworld_SOURCES = helloworld.h helloworld.cc main.cc
I guess this type of makefile is to be used with automake, but, like I said in my firt post, it doesn't automatically work by merely typing that
After reading some on the web, I got the idea I need a configure.in file. This is what I cobbled together:
I have no idea if this is correct, and I still get errors with it present.
I checked, and Synaptic Package Manager did get libgtkmm-2.4-dev. No need to apologize for asking something simple! These are computers after all, not plugging it into the AC outlet will prevent anything from working, after all
When I study the terminal output after running make or g++, I am pretty convinced that the #include
s are targetting .h files in the wrong directories.
"/usr/lib/gtkmm-2.4/gtkmm/button.h" is the correct path to "button.h"
in helloworld.h, it has
if I change it to
the compiler/linker doesn't complain "gtkmm/button.h: No such file or directory"!
I think this is the core problem.
I ran your command line, and this was the first error
g++: pkg-config gtkmm-2.4 --cflags --libs: No such file or directory
I don't really know what pkg-config does, but I hope it has something to do with telling make/g++ where to look for header files!
(Update as I was typing)
I tried the command line again, having carefully read it again, and I put ` instead of ' around the part with pkg-config, and it worked
without any errors or warnings... I saw my first GTK window
I know what g++ does and its basic arguments that it takes, now I am super-interested in this nice little `pkg-config gtkmm-2.4 --cflags --libs` .... please tell me about it!