On Mon, 3 Mar 2008, Bill Janssen wrote:
#!/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
Hmmm. Contrary to the JCC README, this does not result in an egg.
The .so file gets built, but no packaging is done.
What's the quote ?
An egg is only built by setuptools which is imported when it is found.
The only control over egg-or-not I have is whether I import setuptools
instead of distutils as is done on jcc's setup.py and python.py when
building extensions with jcc.
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
