[bt-devel] On Linux too?

[Gary Holmlund]

Eeli Kaikkonen wrote:
> On Mon, 1 Feb 2010, Eeli Kaikkonen wrote:
>   
>> I may have found the Windows problem, too. The search for the modules is
>> stopped if there's mods.d directory in $SWORD_PATH. We use that env
>> variable if it's found. Therefore, if the BibleCS is installed, the
>> engine doesn't find modules installed elsewhere. Gary, am I right?
>>
>> Doesn't this also destroy the idea of adding e.g. CD or USB stick
>> locations, because they can't be used if $SWORD_PATH is used? Does the
>> engine really work this way?
>>     
>
> No, I don't know if it really works this way. I'll try to find it out
> but appreciate any help, especially on the Windows port.
>
> The locale problem seems to have a solution. The engine documentation
> isn't quite correct, it doesn't mention the LocalePath in the
> sword.conf. I found it in our own code. It just isn't used on Linux,
> Gary has written it for Windows. I hope it works there.
>   
Eeli,

Sorry I have not had much time this weekend to look at this. I am 
getting ready to go to work so I will try to get a short answer now and 
spend more time on this issue tonight.

We have a unique requirement on Windows. There is no standard location 
for sword and its locales. We include the sword locales in our 
installation package (c:\Program Files\BibleTime\share\sword\locales.d).

To make sword find this we must control the sword startup. During Bt 
startup we set the current working directory to $HOME/Sword where $HOME 
is defined to be:

APPDATA=C:\Documents and Settings\<username>\Application Data  (on 
windows xp)

We have a sword.conf there which defines the location of locales.d. The 
$HOME/Sword/sword.conf should look like this:

[Install]
DataPath=C:\Documents and Settings\All Users\Application Data\Sword
LocalePath=C:\Program Files\BibleTime\share\sword

With this BibleTime should look for modules at $HOME/Sword and at the 
"DataPath" above. If another directory is added using our bookshelf 
manage, it will appear as an AugmentPath in the $HOME/Sword/sword.conf 
file.

This is how it is supposed to work. I will look further at this tonight.

Gary