jacob berkman wrote:
You probably don't always want to use the same path for all module types. Having support for searching a module path might be useful though (both searching for a particular module, and enumerating all modules on the path).hi, this patch lets libglade search a path for its modules. this allows people w/o write access to /usr install their own glade modules in their home directory, among other things. this basically steals the gtk module finding code. i'd like to see a function in gmodule which does this for one shared env var (G_MODULE_PATH) such that each library doesn't need to implement it, but i assume it's too late to get this into 2.0. if so, i'll do a patch for gmodule 2.2.
anyway, does this look ok to commit?
Looks okay. James. -- Email: james daa com au WWW: http://www.daa.com.au/~james/