Once I fixed my mistake, I used the Xiphos Module Manager to install
from a local folder. I pointed it to the folder containing my mods.d and
modules folders and it installed correctly this time. (This is where I
would have expected some helpful error message previously when the conf
file had a
Perhaps I missed a step, but previously he had specifically said he
was using the Xiphos "local source" option, which is using SWORD to do
the installation.
On Fri, Oct 1, 2010 at 3:41 PM, Troy A. Griffitts wrote:
>
> Well, in your case it is neither. You manually installed the module.
> The aut
Well, in your case it is neither. You manually installed the module.
The auto installer in SWORD to which Matthew is referring will install
from one local repository to another or from a remote repository to
another, but you didn't use the installer to do any of this. You copied
the files in plac
> Is it Sword code or Xiphos code that does the actual installation?
Sword.
Matthew
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above
Ha, I don't know how many times I looked at that and didn't see it! But
I had presumed it must be something simple (although an error message at
module installation would have helped :-) ).
Is it Sword code or Xiphos code that does the actual installation?
All working now -- I'm now a USFM->Sw
If I remember right, I think you have .modules at the start of your
DataPath. It should be ./modules
On 10/01/2010 09:23 AM, Robert Hunt wrote:
> Ok, I still haven't won this one. I think I now have my files in the
> correct structure as per Nic's diagram. Xiphos now finds my files and
> gives no
Ok, I still haven't won this one. I think I now have my files in the
correct structure as per Nic's diagram. Xiphos now finds my files and
gives no errors installing the module when I point it to the folder
containing the mods.d and the modules folders. But it doesn't copy any
files into .sword
Ok, that worked. :-)
Thank you. It wasn't clear to me from the wiki that you have to create
all those levels of structure at the "server" end. It certainly didn't
mention the mods.d folder that I remember.
Blessings,
Robert.
On 30/09/10 20:58, Nic Carter wrote:
Hi Robert,
On 30/09/10 06:00, Robert Hunt wrote:
> 1/ Should the config file be placed in the same folder as the .bz*
> files? (I can't see that the wiki tells me where to put the file.)
You have seen Nic's suggested structure.
>
> 2/ Does the DataPath directive indicate where to *find* the mod
Hi Robert,
I'm no modules expert, but I have a nice little pic I did for someone a few
months ago with the structure of a module.
http://crosswire.org/pocketsword/img/module-zip-structure.png
take a look and see if that helps? Note that the folders may be named
differently, but the "modules"
I've had fun with a USFM New Testament, converted it to OSIS using the
Perl script and then to a module using osis2mod. So far, so good...
However, I can't get Xiphos (on Ubuntu) to recognize either the
compressed or uncompressed module when I add a local folder name and
then choose it. The Mo
11 matches
Mail list logo
