Running GTK+ Applications 3 GTK Library Running GTK+ Applications How to run and debug your GTK+ application All GTK+ applications support a number of standard commandline options. These are removed from argv by gtk_init(). Modules may parse and remove further options. A list of modules to load in addition to those specified in the GTK_MODULES environment variable. Make GTK+ abort on all warnings. This is useful to stop on the first warning in a debugger, if your application is printing multiple warnings. It's almost always best to start debugging with the first warning that occurs. A list of debug options to turn on in addition to those specified in the GTK_DEBUG environment variable. This option is only available if GTK+ has been configured with --enable-debug=yes. A list of debug options to turn off. This option is only available if GTK+ has been configured with --enable-debug=yes. The following options are really used by GDK, not by GTK+, but we list them here for completeness nevertheless. Sets the program class; see gdk_set_program_class(). Sets the program name. A list of debug options to turn on in addition to those specified in the GDK_DEBUG environment variable. This option is only available if GTK+ has been configured with --enable-debug=yes. A list of debug options to turn off. This option is only available if GTK+ has been configured with --enable-debug=yes. The name of the X display to open instead of the one specified in the DISPLAY. This option is only available if GTK+ has been configured with --gdk-target=x11. Makes all X requests synchronously. This is a useful option for debugging, but it will slow down the performance considerably. This option is only available if GTK+ has been configured with --gdk-target=x11. The host to contact the gxid daemon on; overwrites the GXID_HOST environment variable. This option is only available if GTK+ has been configured with --gdk-target=x11. The port for the connection to gxid; overwrites the GXID_PORT environment variable. This option is only available if GTK+ has been configured with --gdk-target=x11. GTK+ inspects a number of environment variables in addition to standard variables like LANG, PATH, HOME or DISPLAY; mostly to determine paths to look for certain files. If GTK+ has been configured with --enable-debug=yes, this variable can be set to a list of debug options, which cause GTK+ to print out different types of debugging information. misc Miscellaneous information text Information about text widget internals tree Information about tree widget internals updates Visual feedback about window updates The special value all can be used to turn on all debug options. A list of modules to load. Specifies a list of directories to search when GTK+ is looking for dynamically loaded objects such as the modules specified by GTK_MODULES, theme engines, and input method modules. If the path to the dynamically loaded object is given as an absolute path name, then GTK+ loads it directly. Otherwise, GTK+ goes in turn through the directories in GTK_PATH, followed by the directory .gtk-2.0 in the user's home directory, followed by the system default directory, which is libdir/gtk-2.0/modules. (If GTK_EXE_PREFIX is defined, libdir is $GTK_EXE_PREFIX/lib. Otherwise it is the libdir specified when GTK+ was configured, usually /usr/lib, or /usr/local/lib.) For each directory in this list, GTK+ actually looks in a subdirectory directory/version/host/type Where version is derived from the version of GTK+ (use pkg-config --variable=gtk_binary_version gtk+-2.0 to determine this from a script), host is the architecture on which GTK+ was built. (use pkg-config --variable=gtk_host gtk+-2.0 to determine this from a script), and type is a directory specific to the type of modules; currently it can be modules, engines or immodules corresponding to the three types of modules above. Either version, host, or both may be omitted. GTK+ looks first in the most specific directory, then in directories with fewer components. The components of GTK_PATH are separated by the ':' character on Linux and Unix, and the ';' character on Windows. Specifies an IM module to use in preference to the one determined from the locale. Specifies the file listing the IM modules to load. This environment variable overwrites the im_module_file specified in the RC files, which in turn overwrites the default value sysconfdir/gtk-2.0/gtk.immodules (sysconfdir is the sysconfdir specified when GTK+ was configured, usually /usr/local/etc.) Specifies a list of RC files to parse instead of the default ones; see Resource Files. If set, GTK+ uses $GTK_EXE_PREFIX/lib instead of the libdir configured when GTK+ was compiled. If set, makes GTK+ use $GTK_DATA_PREFIX instead of the prefix configured when GTK+ was compiled. The following environment variables are used by GdkPixbuf, GDK or Pango, not by GTK+ itself, but we list them here for completeness nevertheless. Specifies the directory to look for GdkPixbuf loader modules. By default, GdkPixbuf looks for its loaders in libdir/gtk-2.0/version/loaders. If GTK+ has been configured with --enable-debug=yes, this variable can be set to a list of debug options, which cause GDK to print out different types of debugging information. misc Miscellaneous information events Show all events received by GDK dnd Information about drag-and-drop xim Information about XIM support The special value all can be used to turn on all debug options. The host and port to contact the gxid daemon on. gxid is only necessary on X servers which don't support using the pointer and extension devices at once, and is only built if GTK+ is configured with --with-xinput=gxi. The XFree86 X servers don't have this restriction. If this variable is set to 1, GTK+ will use the Pango Xft backend instead of the X backend when possible (i.e. when the X server supports the XRender extension and Pango has been built with Xft support).