GNOME Bugzilla – Bug 47053
GNOME-VFS should be able to compile without modules (configure-time option)
Last modified: 2008-09-06 18:54:07 UTC
on 2/25/01 11:06 PM, Joe Shaw at joe@ximian.com wrote: > Is it possible to link gnome-vfs statically? Other libraries that use > gmodule to dynamically load modules (like gdk-imlib and gdk-pixbuf) there > is a --disable-modules configure option that makes this easy. Does this > exist for gnome-vfs, and if not, can such a thing be added? It doesn't exist. I think it would be relatively easy to add it some day. This is the first time I've ever heard this suggestion. It does seem like a good idea -- I wasn't aware of that feature of gdk-pixbuf. I think a bugzilla.gnome.org bug report with a mention of this feature and why it's useful would be the best way to get this on the minds of the people who actively maintain gnome-vfs. Of course this feature is probably going to be more useful when we get rid of the other dynamic linking used in gnome-vfs. Currently it dynamically links to either the thread or CORBA back end for async. operations. But the CORBA back end is obsolescent and slated to be removed. When we do remove it we can get rid of the dynamic linking to the back end. ------- Additional Comments From snickell@stanford.edu 2001-07-23 00:36:23 ---- Taking bugs previously assigned to Pavel, assigning them to myself. Will parse them out at my leisure , but many are GnomeVFS bugs we should look at for 2.0 ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:03 -------
We'd like to do this but it's unlikely to happen soon unless someone contributes the code.
reassigning this back to owner
Implementation: --with-included-filesystems Static inclusion of filesystem modules to the main libgnomevfs-2. Used for fully static GNU/Linux distribution independent binaries. It may be also useful for Gnome OS based embedded network devices. Patch based on --with-included-modules of Pango and inspired by --disable-modules/--with-included-loaders of GTK+. Name of the included filesystem is assumed to be both its own 'module name' and 'method name' to prevent the dependency on GnomeVFS configuration files (prevented by Bug # 127114). 'module name'->'method name' assumption is not the case for the regular .so modules. (removed my DUPe Bug # 127115)
Created attachment 21501 [details] [review] --with-included-filesystems implementation patch
*** Bug 127115 has been marked as a duplicate of this bug. ***
Created attachment 56199 [details] [review] --with-included-filesystems implementation patch for 2.10.0-5 Years pass, packages change, patches keep up to date themselves. Have you heard the spring will come again?
Created attachment 56427 [details] [review] --with-included-filesystems patch for 2.10.0-5 (fixed external #include-ing)
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome. If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs. @Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of this notification noise all together. General further information: http://en.wikipedia.org/wiki/GVFS Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html