Re: [sword-devel] Release 1.8.1

2018-04-23 Thread Greg Hellings 
On Mon, Apr 23, 2018, 15:46 Robert Hunt  wrote:

> Hi Greg and others,
>
> Just a couple of questions:
>
> I just rebuilt my Sword installation on Ubuntu using cmake (after getting
> the latest revision 3581 with svn) without problems. But I was surprised
> that the new osis2mod has the same revision number as a year ago (still
> r3431). Does this mean it hasn't changed in that time (except for library
> changes)?
>
An svn log of the file should tell you.

> I also rebuilt my Python bindings and get this:
>
> Tue 08:19:$ python3
>
> That's cool. I have plans to verify that the bindings are compatible with
Python 3. So it's good to know that they are!

> Python 3.6.5 (default, Apr  1 2018, 05:46:30)
> [GCC 7.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import Sword
> >>> print( 'version', Sword.SWVersion().getText() )
> version 0.0
> >>> print( "Versions", Sword.SWVersion().major, Sword.SWVersion().minor,
> Sword.SWVersion().minor2, Sword.SWVersion().minor3 )
> Versions 0 0 -1 -1
> >>>
>
> I can't remember (or now find) what the previous behaviour was, but I'm
> guessing this is a regression or at least a bug?
>

I haven't the least idea on that. I don't really use the bindings. I just
maintain them! You could check out the appropriate version from the past to
check. Maybe a git bisect could be helpful. 😂

--Greg


> Thanks,
> Robert.
>
> On 09/01/18 16:05, Greg Hellings wrote:
>
> I would also like to add that the release process can be seen here:
>
> http://ci.crosswire.org/job/sword-release/18/
>
> --Greg
>
> On Mon, Jan 8, 2018 at 9:03 PM, Greg Hellings 
> wrote:
>
>> Coming quickly on the heels of 1.8.0, I'm happy to announce the release
>> of the engine's 1.8.1 release. This release primarily comprises some
>> updates to the bindings, including fixing the SWIG bindings to compile
>> against the 1.8 series and a few fixups to the CMake scripts relating to
>> testing.
>>
>> Please find the detailed information below:
>>
>> MD5: ddab24192104b15cbec72e569145ccd1 sword-1.8.1.tar.gz
>>
>> SHA512:
>> 5c08c070ea0c86b7d929bbf94c89730eb5a487986deb9edf01c08d1710356aecd1ab3bde4437a778e5fc1ceb05b63287612ec6161381c0986a36344c27d2ab36
>> sword-1.8.1.tar.gz
>>
>> http://crosswire.org/ftpmirror/pub/sword/source/v1.8/sword-1.8.1.tar.gz
>>
>> --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
___
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

Re: [sword-devel] Release 1.8.1

2018-04-23 Thread Robert Hunt 

  
  
Hi Greg and others,
Just a couple of questions:
I just rebuilt my Sword installation on Ubuntu using cmake (after
  getting the latest revision 3581 with svn) without problems. But I
  was surprised that the new osis2mod has the same revision number
  as a year ago (still r3431). Does this mean it hasn't changed in
  that time (except for library changes)?
I also rebuilt my Python bindings and get this:

  Tue 08:19:$ python3
Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more
information.
>>> import Sword
>>> print( 'version', Sword.SWVersion().getText() )
version 0.0
>>> print( "Versions", Sword.SWVersion().major,
Sword.SWVersion().minor, Sword.SWVersion().minor2,
Sword.SWVersion().minor3 )
Versions 0 0 -1 -1
>>> 
  

I can't remember (or now find) what the previous behaviour was, but
I'm guessing this is a regression or at least a bug?

Thanks,
Robert.

On 09/01/18 16:05, Greg Hellings wrote:


  I would also like to add that the release process
can be seen here:


http://ci.crosswire.org/job/sword-release/18/



--Greg
  
  
On Mon, Jan 8, 2018 at 9:03 PM, Greg
  Hellings 
  wrote:
  

  Coming quickly on the heels of 1.8.0, I'm happy to
announce the release of the engine's 1.8.1 release. This
release primarily comprises some updates to the
bindings, including fixing the SWIG bindings to compile
against the 1.8 series and a few fixups to the CMake
scripts relating to testing.
  
  
  Please find the detailed information below:
  
  
  MD5: ddab24192104b15cbec72e569145ccd1
  sword-1.8.1.tar.gz
  
  
  SHA512: 5c08c070ea0c86b7d929bbf94c89730eb5a487986deb9edf01c08d1710356aecd1ab3bde4437a778e5fc1ceb05b63287612ec6161381c0986a36344c27d2ab36
sword-1.8.1.tar.gz
  
  
  http://crosswire.org/ftpmirror/pub/sword/source/v1.8/sword-1.8.1.tar.gz
  
  
  
  --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

Re: [sword-devel] Android common module storage location

2018-04-23 Thread Karl Kleinpaste 
On 04/23/2018 09:45 AM, Martin Denham wrote:
> You could try putting the modules in the jsword folder as described
> here
> .

That begs several questions.

1. Even if doing so was appropriate -- it's not, see end -- I still need
to know why just "sword" doesn't work, since the bindings code
(bindings/java-jni/jni/swordstub.cpp) suggests it should.
2. As a practical matter, when I rename sword to jsword, Bishop stops
being able to find modules (it's not JSword-driven), and AB reproducibly
chokes: "Unfortunately, And Bible has stopped.  OK/REPORT"  I brought in
my entire module set, ~800 -- is AB's failure a capacity problem, being
unprepared for a big set?
3. Android is a platform that has been alive less than half the time of
Crosswire itself, yet we have 3, competing, apparently conflicting
places in the filesystem in which to put modules. Could we prettyplease
/immediately/ standardize on exactly /one/ place, and have all Android
apps move to that ASAP? There's only maybe 3, right? Bishop, AB, and
BibleTime Mobile?

O frabjious joy. BTM also doesn't find modules in sword.

If /sdcard/sword isn't going to work right now, where does one put
modules, so that they are findable by all of Bishop, AB, and BTM? Does
one such place exist? I won't duplicate my module set per-app, it's
5.3G. I can afford that space on this device once, but I won't spend it
twice.

The use of the "jsword" name is wrong as a matter of software
engineering principle, from the standpoint that it references
exclusively a particular engine, and not "a cache of modules to be
handled by any Crosswire app, i.e. Sword as a whole" when more than 1
such app can be installed, all of which need to share them, regardless
of engine. There is nothing JSword-specific about module content.
___
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

Re: [sword-devel] Android common module storage location

2018-04-23 Thread Martin Denham 
You could try putting the modules in the jsword folder as described here

.

Martin

On 23 April 2018 at 12:36, Karl Kleinpaste  wrote:

> I'm trying to figure out why I can't get Bishop and AndBible to see the
> same module set.
>
> I've got my modules in (what is perceived as, via File Manager) "/Internal
> storage/sword". Now, from an ftp client poking around the local filesystem,
> this appears as /storage/emulated/0/sword.
>
> However, that's somewhat unreal, too, because if I poke upward in the
> filesystem far enough, I discover that I can reach /sdcard, which contains
> what's seen originally, so that I can refer to /sdcard/sword. Using a
> terminal emulator, termux, I learn that /sdcard is a symlink to
> /storage/self/primary.
>
> Well, fine so far, actually: I have my modules in an identifiable place.
> On Troy's reference, I find this in Sword bindings:
>
> static char *SWORD_PATH = "/sdcard/sword";
> static char *AND_BIBLE_MODULES_PATH = "/sdcard/Android/data/net.
> bible.android.activity/files";
>
> Termux will let me "cd /sdcard/sword" just fine, or use
> /storage/self/primary/sword equivalently.
>
> So why doesn't AndBible find my modules? It's insisting on starting from
> scratch, and simply exits if I decline. For some reason, it doesn't see (or
> isn't using) the perfectly acceptable /sdcard/sword.
>
> Otherwise, can someone give an acceptable Android UI way to say the
> equivalent of
> mv /sdcard/sword/mods.d/* /sdcard/Android/data/net.
> bible.android.activity/files/mods.d/"
> and so forth?
>
> ___
> 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

[sword-devel] Android common module storage location

2018-04-23 Thread Karl Kleinpaste 
I'm trying to figure out why I can't get Bishop and AndBible to see the
same module set.

I've got my modules in (what is perceived as, via File Manager)
"/Internal storage/sword". Now, from an ftp client poking around the
local filesystem, this appears as /storage/emulated/0/sword.

However, that's somewhat unreal, too, because if I poke upward in the
filesystem far enough, I discover that I can reach /sdcard, which
contains what's seen originally, so that I can refer to /sdcard/sword.
Using a terminal emulator, termux, I learn that /sdcard is a symlink to
/storage/self/primary.

Well, fine so far, actually: I have my modules in an identifiable place.
On Troy's reference, I find this in Sword bindings:

static char *SWORD_PATH = "/sdcard/sword";
static char *AND_BIBLE_MODULES_PATH =
"/sdcard/Android/data/net.bible.android.activity/files";

Termux will let me "cd /sdcard/sword" just fine, or use
/storage/self/primary/sword equivalently.

So why doesn't AndBible find my modules? It's insisting on starting from
scratch, and simply exits if I decline. For some reason, it doesn't see
(or isn't using) the perfectly acceptable /sdcard/sword.

Otherwise, can someone give an acceptable Android UI way to say the
equivalent of
    mv /sdcard/sword/mods.d/*
/sdcard/Android/data/net.bible.android.activity/files/mods.d/"
and so forth?
___
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