Hello, You can also ship the GTK shared libraries with your application, and dynamically write the various module/pango config files in your installation routine. Then, set the appropriate environment variables so that GTK finds the config files, and you should be good to go. VMWare for Linux uses this approach successfully. ~Jesse riboaz@xxxxxxxxx on May 4, 2005 wrote: > thanks for the follow-up. > > but to split hairs: compiling statically is very useful, then i can > deliver my application without the user being required to have gtk+ > installed on their platform. (because when an end-user is not OS-savvy, > installing gtk+ can ultimately mean my application will never run since > they may not be able to successfully install gtk+. and i must imagine > that the designers of gtk+ did never intend that applications built with > gtk+ aren't runnable simply because the end-user doesn't have access to a > techie.) > > so my question remains: is it possible? was it ever thought of in the gtk+ > design to allow for this possibility? or is it such that because the > resulting static application would be necessarily "heavy" (or for any > number of other reasons) this is simply not possible? > > thanks, > > richard _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
