Hi Greg,
The Sword binding is C++ and the main application is Javascript
(Electron / Node-JS).
Main application:
https://github.com/tobias-klein/ezra-project
Sword interface:
https://github.com/tobias-klein/ezra-sword-interface
Besides Github the Sword interface is also published on npmjs.com, which
means it can be easily installed with npm (node package manager).
https://www.npmjs.com/package/ezra-sword-interface
The main application depends on the most recently published version of
the Sword interface and the dependency is handled by npm.
When installing the dependencies of Ezra Project (see step 2 below) the
correct version of the Sword interface is automatically installed in the
project directory (from npmjs.com).
To get Ezra Project and its Sword interface setup/compiled, the
following steps must be performed (on Debian/Ubuntu):
0) Install tool/library dependencies: nodejs, build-essential,
libsword-dev, libsqlite3-0
1) Clone Ezra Project (https://github.com/tobias-klein/ezra-project.git)
2) Install dependencies in the Ezra Project directory: Run "npm install"
in project directory
3) Rebuild C++ dependencies: Run "npm run rebuild-linux" in project
directory
4) Start ezra project: Run "npm start" in project directory
I should put these instructions on the Wiki pages on Github as well ...
will do that asap.
Have a blessed Easter celebration! The Lord is risen!
Best regards,
Tobias
On 17.04.19 23:39, Greg Hellings wrote:
Tobias,
What form is your code in? Where does the repo live? Is it a C/C++
app? A Python app?
--Greg
On Wed, Apr 17, 2019 at 3:27 PM Tobias Klein <[email protected]
<mailto:[email protected]>> wrote:
Mmmm... I guess you're right about that. Maybe a step before going
"into" the repositories is to offer debian packages for regular
download.
Best regards,
Tobias
On 17.04.19 09:00, [email protected] <mailto:[email protected]> wrote:
I am not sure what you try to achieve. At the moment people who
use your app are fellow developers and others like me who compile
gladly ourselves. If you want ordinary users get it into the
repos. Then the lib linkage problem goes away too.
Sent from my mobile. Please forgive shortness, typos and weird
autocorrects.
-------- Original Message --------
Subject: [sword-devel] Linux: Linking to Sword library with
potentially different names
From: Tobias Klein
To: SWORD Developers' Collaboration Forum
CC:
Hi,
I need some advice from you Linux experts.
Cyrille tested Ezra Project on Linux and couldn't run it,
because the
Sword package on that system (custom Sword 1.8.1 on Ubuntu
18.04)
contains a differently named *.so file than on my system
(Default Sword
package from Ubuntu 18.04 => libsword11v5).
What can I do to support multiple *.so variants with the same
binary? Is
there a way to do that?
I was thinking about creating a symlink within my application
directory
structure that can be adjusted at runtime based on some
dynamic system
inspection code.
Best regards,
Tobias
_______________________________________________
sword-devel mailing list: [email protected]
<mailto:[email protected]>
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list:[email protected]
<mailto:[email protected]>
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: [email protected]
<mailto:[email protected]>
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
