[pylucene-dev] Windows Python 2.5 binaries?

[Andi Vajda]

On Wed, 11 Oct 2006, Steven Bethard wrote:

> Ok, I'm stuck.  I dowloaded:
>
>   http://downloads.osafoundation.org/PyLucene/src/PyLucene-src-2.0.0-3.tar.gz
>
> And followed the instructions in INSTALL for downloading and
> installing MinGW etc.  I modified the Makefile to uncomment the
> Windows section and fill in the appropriate values (leaving the DB
> stuff commented since I'm not building the Berkely DB support).  When
> I run ``make``, I see:
>
> cd lucene-java-2.0.0-453447; patch -Nup1 < ../patches.lucene; echo ok
> can't find file to patch at input line 3
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |--- 
> lucene-java-2.0.0-434148/src/java/org/apache/lucene/queryParser/QueryParser.java
> 2006-07-23 04:08:36.000000000 -0700
> |+++ 
> lucene-java-2.0.0-434148-patched/src/java/org/apache/lucene/queryParser/QueryParser.java
> 2006-08-23 15:07:01.000000000 -0700
> --------------------------
>
> I noticed that the directory actually created was
> lucene-java-2.0.0-453447 (different last number), and I tried to fix

No need to fix the dirname, -p1 will strip one level of directory name from 
the patch instructions.

> I tried just ignoring the patches.  I then got an error which I
> tracked down to ``ant`` not being installed.  (Apache ant is not
> listed as one of the requirements for building PyLucene.  If it is
> required, it should probably be listed in the INSTALL file.)  I
> installed ``ant`` but then (after ignoring all the patches) I get the
> error:
>
>   Buildfile: build.xml does not exist!
>   Build failed
>
> Suggestions?

The source tarball (as opposed to a complete PyLucene svn checkout) contains 
the .jar files built from already patched Lucene sources. This is to avoid 
requiring Ant and a JDK to build PyLucene from a tarball.

This means that you don't need to patch, run Ant. The build process should 
start from the .jar files included.

My 'Windows' section in PyLucene's Makefile looks like this:

# Windows (with gcj 3.4.6 and libs statically linked)
PREFIX_PYTHON=/cygdrive/o/Python-2.4.3/PCbuild
GCJ_HOME=/cygdrive/o/mingw-5.0-3.4.6
GCJ_LIBDIR=$(GCJ_HOME)/lib
GCJ_STATIC=1
LIB_INSTALL=
#DB=/cygdrive/o/db-$(DB_VER)
#PREFIX_DB=$(DB)
#ANT=ant
PYTHON=$(PREFIX_PYTHON)/python.exe

If the build process doesn't pick up from the .jar -> .o compiling phase, I'd 
check that the files are there and that their dates are correct with regards 
to the make rules that work with them.

Andi..