[pylucene-dev] PyLucene JCC win32 binary for python 2.5

[Andi Vajda]

On Sat, 29 Dec 2007, Charles wrote:

> On Dec 29, 2007 7:20 AM, Andi Vajda <vajda at osafoundation.org> wrote:
>> I built it myself, you can download it from [1].
>>
>> Andi..
>>
>> [1] http://builds.osafoundation.org/compilers/windows/mingw-5.0-3.4.6.tar.bz2
>
> Hi Andy,
>
> Thanks for the link. I will try to compile PyLucene using that
> version. By the way, I am curious why do the size of libgcj.a in your
> mingw build is 87 MB while the size of libgcj.a I downloaded from
> mingw site is only 19.7 MB?

I don't know. Maybe some stuff is stripped ?

You should know that PyLucene with GCJ is on its way to deprecation. One of 
the main reasons I wrote JCC is that building GCJ for Windows is such a huge 
pain and debugging PyLucene there is pretty much impossible. I had to move 
to plan B. GCJ on Intel Mac is a small miracle, the only real activity on 
gcj in the past year or two has been on Linux, almost exclusively. Linux is 
only one of three OSs I have to support, though.

Furthermore, the open sourcing of Java by Sun and the resulting lack of 
activity (gauged by the much smaller amount of traffic on the gcj mailing 
list) on the gcj/libgcj front is another big motivator. JCC replaces CNI 
adequately and generates all the python wrappers as well. The GCJ PyLucene 
C++ wrappers, tens of thousands of lines of code, are handwritten. PyLucene 
with JCC is completely machine generated (except for the few extension stub 
Java classes that are still hand written).

I've had too many weird/random Windows only bugs that I've simply had to 
give up. PyLucene with JCC is a lot more stable, predictable and tunable.
It's also backed by sane VMs instead of so-so libgcj.

Anyhow, you're certainly welcome to build PyLucene with GCJ but now you 
know... I don't intend to do much work on the GCJ side of PyLucene anymore.

Andi..