On 10/11/06, Andi Vajda <[EMAIL PROTECTED]> wrote:
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.
Running make -d with a Makefile that looks pretty much like the one
above, I see that:
Prerequisite `lucene-java-2.0.0-453447' is newer than target
`lucene-java-2.0.0-453447/build/lucene-core-2.0.0-453447.jar'.
Looks like it expects the directories to have the same dates, but when
I extract the files (either with 7-zip or GnuWin32 tar/gzip) I get
folders with newer modification dates than all the jar files. I ran
the following script to ``touch`` everything:
import os
import subprocess
for base_path, file_names, dir_names in os.walk('.'):
for name in file_names + dir_names:
path = os.path.join(base_path, name)
subprocess.call(['touch', path])
and got a little farther. I got some errors due to the space in
"Program Files" in my PREFIX_PYTHON, so I replaced that with
"PROGRA~1", and I got some other errors because I unzipped and tried
to compile PyLucene from within a directory that had a space in it.
After moving everything to a spaceless directory and running make
again, I now get the error:
/cygdrive/d/MinGW/bin/g++ -shared -o release/_PyLucene.pyd ...
`cygpath -aw /cygdrive/c/PROGRA~1/Python/python25.dll` -L`cygpath -aw
/cygdrive/d/MinGW/lib` -lgcj -liconv -lwin32k -lws2_32
g++.exe: c:\PROGRA~1\Python\python25.dll: No such file or directory
I used the MSI installer from python.org when I installed Python2.5
and as far as I could tell, it doesn't seem to install a python25.dll.
Where should that be coming from? (There is a python25.lib in
C:\PROGRA~1\Python\libs for what it's worth.)
Steve
--
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a
tiny blip on the distant coast of sanity.
--- Bucky Katt, Get Fuzzy
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
