On Mon, 3 Mar 2008, Bill Janssen wrote:
So, here's what I'm trying, to build the egg without installing JCC
(this is OS X only, for the moment). I'm starting with a PyLucene
source distribution:
Why are you building the PyLucene egg without installing JCC ?
JCC is installed in a different, separate egg anyway (see your site-packages
directory). You're just making the PyLucene build harder than it needs to
be. To run PyLucene, the JCC is _not_ necessary nor is it used. We don't
distribute it with Chandler either. The JCC runtime code needed by PyLucene
is linked into the _lucene.so extension already.
#!/bin/csh
echo "building PyLucene egg..."
cd /tmp
tar xvfz /prereqs/PyLucene-*.tar.gz
cd ./PyLucene-*/jcc
/usr/bin/python setup.py build
cd ..
setenv PYTHONPATH ./jcc/build/lib.macosx-10.5-i386-2.5
make PREFIX_PYTHON=/usr ANT=ant PYTHON=/usr/bin/python JCC="/usr/bin/python
./jcc/build/lib.macosx-10.5-i386-2.5/jcc/__init__.py" NUM_FILES=1 compile
find ./build -name \*.egg
Now, my next question is, given a Mac without setuptools installed on
it (10.4 with Python 2.3.5), can I install an egg on it somehow
manually? Or do I need a different build technique for Tiger? I
guess I'll ask this on the Python distutils list.
When you distribute the lucene egg (anywhere), don't forget to distribute
the lucene.pth file as well. It is responsible for letting Python know that
the 'lucene' package corresponds to the rather lengthy and complicated
lucene.......egg directory in site-packages.
I doubt that Python 2.3.5 without setuptools is capable to resolve this but
I could be wrong. Best it to try it.
Of course, the distutils mailing list might have other ideas...
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
