[sword-devel] Clucene .09.23 and Sword 1.6.0 / 1.6-svn -Compiling Help

Nathan Anderson nathan at andersonsplace.net
Mon Oct 19 10:28:26 MST 2009


	Thanks for letting me know -- I kinda wondered if that was the case.
I have already deb-ized the .21b for this device to get something going.
When I have some free time; I will come back and work on understanding what
sword needs from Clucene and will attempt to make a #DEFINE able patch to
allow .23 or .21 to work.  

	As for indexes, I'm not sure -- I understand .21 is compatible with
1.8/9 branch of Jlucene.  But .23 is compatible with 2.3.2 branch of Jlucene
and that version of J/C Lucene is much faster, with if, I recall correctly,
a slightly lower memory footprint.  Since the device I'm working with is a
low memory and a embedded arm chip; faster and lower memory requirements is
a very (very) nice perk.  ;-)


-----Original Message-----
From: Matthew Talbert [mailto:ransom1982 at gmail.com] 
Sent: Monday, October 19, 2009 12:02 PM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Clucene .09.23 and Sword 1.6.0 / 1.6-svn
-Compiling Help

>        I'm working on porting the whole stack to another device that 
> does not have any of the libraries yet.   I will "use" 21b if I have 
> to to get past the issue.  But I would love to use .23 if possible.

I think it would be great to have support for .23. As far as I know, no one
has worked on this at all. It is important (imo) to keep compatibility with
21b, as that is what will be in all the linux distros until .23 is marked
stable. I would be interested in trying out .23 on Windows though, if it
proves to be reasonably stable (I have no clue if the indexes it creates are
compatible with .21b; that could be an issue).


sword-devel mailing list: sword-devel at crosswire.org
Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list