On Thu, Dec 18, 2008 at 11:44 PM, Troy A. Griffitts <scr...@crosswire.org> wrote: > Our engine has a number of ways which it can be configured and these all > work on all platforms. We don't remove support for some ways of > configuration on certain platforms-- including $HOME/.sword. If you have > something there, then it will do the appropriate SWORD thing (in the case of > $HOME/.sword it will augment any other configuration location found by > adding modules found here). I use the same file system and SWORD library > install on a number of system. It's fun. Try adding an /etc/sword.conf to > your windows drive :) Don't use it if you think it shouldn't be there on > windows. > > The appropriate response to where modules are officially found on any OS by > the SWORD engine (should also be with JSword as well) is: > > http://crosswire.org/svn/sword/trunk/INSTALL > under the DETAILS section. > > We should stay unified on this (and other things). > > These many configuration options allows OS friendly locations by letting any > app installer either include a ./sword.conf which specifies where to look > for modules, or else setting env SWORD_PATH (if they don't like the other > default locations scanned).
Back when I was trying to work on a wxWidgets sword client, I was able just to set SWORD_PATH to the installation location for BibleCS, and it found the modules installed perfectly fine. It sure seems like that's the way to go! --Greg _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
