On 08/16/10 15:29, Enrico Weigelt wrote: > It grows as soon as certain pages are accessed. And - as already said - > unless the distinct functional (sub)modules are aligned into their > own pages instead of randomly cat'ed to one big contigious text section > on linker's will, there's great chance that there're many, many > never-accessed areas within pages that still have to be accessed > (and thus loaded).
So, doesn't gtk's code breakdown by functionality and the file naming convention automatically provide such a submodule hierarchy? All the linker has to do is to link them in the order provided on the commandline. Then all of the following will be in a big unused chunk if you don't use the filechooser stuff: gtkfilechooser.lo gtkfilechooserbutton.lo gtkfilechooserdefault.lo gtkfilechooserdialog.lo gtkfilechooserembed.lo gtkfilechooserentry.lo gtkfilechoosersettings.lo gtkfilechooserutils.lo gtkfilechooserwidget.lo gtkfilefilter.lo gtkfilesel.lo gtkfilesystem.lo gtkfilesystemmodel.lo behdad _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list