You need a sword.conf for libsword to know where to look for modules. You also need to refresh all remote sources first.
Peter
Gesendet: Freitag, 28. Juni 2019 um 16:31 Uhr
Von: "Justin Bellars" <jbell...@gmail.com>
An: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Betreff: Re: [sword-devel] Eclectic Questions re: CLI, OSIS markup of Trinitarian referents, and the 1662 BCP as a module
Von: "Justin Bellars" <jbell...@gmail.com>
An: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Betreff: Re: [sword-devel] Eclectic Questions re: CLI, OSIS markup of Trinitarian referents, and the 1662 BCP as a module
Thank you, Pierre!
I must have larger problems, since those commands return "Couldn't find remote source [CrossWire]" I compiled Sword from the makefile, but perhaps there is something missing... I am also running it in Windows Subsystem Linux (WSL - Ubuntu 18.04), so perhaps in a native Linux or BSD environment it would be more straightforward? Perhaps Windows firewalling is getting in the way. I'll keep at it.
Best regards,
Justin
On Thu, Jun 27, 2019 at 8:39 PM pierre amadio <amadio.pie...@gmail.com> wrote:
Hi there !
>> Can someone direct me to common CLI commands for module management everyone should know?
Have a look at installmgr :
installmgr -r CrossWire
installmgr -ri CrossWire KJV
_______________________________________________
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
_______________________________________________ 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
