I sure hope so. The problem was known in Aug. So, I just hope now that more people are using the SDK, that it will become something that has to be fixed.

LOL, sorry, I have no idea on size yet -- I just built debug versions of everything to be able to diagnose issues.

---

Their are some "gotchas" if you want to duplicate what I've done:

CLucene 0.9.23 no longer has the CLBackwards.h header file.
So the sword code has to have that line commented out in one of the files. It doesn't affect anything it was apparently a code cleanup.

CLucene now compiles to libclucene-core and sword expects just libclucene. I had to manually add a symlink. (I need to make sure my "package" will make that symlink )

Several version of sword I had diffeerent issues with -- Sword 1.60 the python bindings will work. 1.6. SVN version bindings didn't work. Also didn't realize Sword required ICU, so until I added it it was a bit wonky. But ICU was simple to get and compile.

I was fighting a stupid rapier/python/hildon bug forever, and I finally just decided to remove the progress bar dialog and change it to a information dialog and bam, I had it working. I was also pleased that I was able to download the Bibles from inside rapier restart it; and it was working fine. So their isn't really any more python code changes "needed" to make it function. (I still need to report this bug to the pymaemo people)

I think I'm going to put this on hold for the moment until we can get the armel building fixed. I might trying compiling Ziphos and Bibletime to see how easy it is to compile in the scratchbox.

I also need to find out about "opt"ifing stuff; I understand libraries are supposed to be optified but I'm not sure what is needed to make that process work. Be nice to actually have a device to test everything on. ;-D

Nathan.