Julien PUYDT a écrit : > Julien PUYDT a écrit : >> Craig Southeren a écrit : >> >>> It could be the plugin code looking for plugins, if the PWLIBPLUGINDIR >>> environment variable is set weirdly >> I think it's the plugin code > > Here it is, from src/ptlib/common/pluginmgr.cxx : > > PStringArray PPluginManager::GetPluginDirs() > { > PString env = ::getenv(ENV_PWLIB_PLUGIN_DIR); > if (env == NULL) { > // env = P_DEFAULT_PLUGIN_DIR; > PString execDir = PProcess::Current().GetFile(); > PINDEX sepLoc = execDir.FindLast(PDIR_SEPARATOR); > if(sepLoc != P_MAX_INDEX){ > execDir = execDir.Left(sepLoc); > } > env = execDir + DIR_SEP + P_DEFAULT_PLUGIN_DIR; > } > > // split into directories on correct seperator > return env.Tokenise(DIR_SEP, TRUE); > }
What it should do is : - get the env variable ; - if it's set, use that ; - if it isn't : - build a list from : - the P_DEFAULT_PLUGIN_DIR, which *MUST* be a single absolute directory path ; - a more local directory, which will be found from the home dir on unix-likes, and from the exec dir on win32 (but won't be all of that dir -- probably some env = homedir + DIR_SEP + ".pwlib" + DIR_SEP + "plugins"!) Would that fly ? Snark _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list