It's pretty skinny. Looking at some of the tutorial examples, after strippig the (dynamic) executables, we get the following sizes (on a RH 6.0 system, using egcs 2.91.66, not using any Gtk themes):
Gtk vs gtkmm resource consumption comparison
Example | Gtk+ File Size | Gtk+ Memory | gtkmm File Size | gtkmm Memory |
---|---|---|---|---|
buttons | 6256 | 1844 | 30996 | 2820 |
clist | 7720 | 1900 | 32012 | 2840 |
filesel | 5496 | 2076 | 27820 | 3052 |
progressbar | 9844 | 1916 | 34056 | 2932 |
rulers | 6632 | 1812 | 24300 | 2740 |
where GTK+File is the file size and GTK+Mem the resident memory size of the GTK+ executables; and gtkmmFile and gtkmmMem the respective sizes of the gtkmm executables.
C++ executables are necessarily larger than C executables since they require all sorts of info in order to properly link (dynamic) class structures at run time. All Unices today are clever enough to actually load in memory only what is needed. Therefore, a large executable and large dynamic libraries do not necessarily mean large memory consumption.