>
> We add "AbsoluteDataPath" as a config entry when we load the
> configuration of modules to help with things similar to this, so you can do:
>
> module->getConfigEntry("AbsoluteDataPath");
>
> to tell you where the module data lives. Though this will not officially
> help you find the config, it
Matthew,
If you are using InstallMgr, then there is a facility for this in the
virtual method getCipherCode.
The relevant example from our BibleCS code is
http://crosswire.org/svn/biblecs/branches/BCB5/apps/InstallMgr/MainFrm.cpp
bool InstallMgrWin::getCipherCode(const char *modName, SWConfig *
On 23 May 2010 01:06, Matthew Talbert wrote:
> So, my first question is, "what is the best way to get the conf file
> for a given module?" and the second is, "could we please add this to
> the engine?"
>
The best way is probably to store sword configurations according to
XDG base-dir spec.[1]
It
I'm writing gobject bindings for SWORD, which consists of refactoring
most of our backend code that we've used for a long time in Xiphos.
Part of the code we have is to set the cipher key for a module. In
looking at that, I don't see an easy way to get the .conf file for a
particular module. We eve
