On Wed, 16 Apr 2008, Jeff Breidenbach wrote:
I've packaged the current PyLucene. It's very preliminary, there are tons to things to adjust, highly untested, etc. etc. It's in http://www.jab.org/pylucene with an AMD64 build done on Ubuntu Gutsy. Quick questions: Is there a good way to get jcc source separate from PyLucene? That's helpful as I need build those two packages separately due to the dependency between them. Currently I'm just slicing and dicing the pylucene tarball.
The JCC source tree is at [1] inside the PyLucene/jcc source tree [2]. [1] http://svn.osafoundation.org/pylucene/trunk/jcc/jcc/ [2] http://svn.osafoundation.org/pylucene/trunk/jcc/
There's a bit in setup.py in jcc, where one has to switch things around if one is on AMD64 linux2 vs. i386 linux2. Is there any way to make that automatic? This would be helpful for autobuilders and I don't know enough python to pull it off. Patch appreciated; no need to put this in the canonical source release.
There is nothing automatic unless someone contributes the python code for setup.py to make it so. But you can skip editing setup.py by setting instead the corresponding env variables such as JCC_INCLUDES, JCC_CFLAGS, JCC_LFLAGS before calling setup.py.
I'm sure I'll have more questions, but that's it for now. Feel free to critique. Not recommended for actual use at this point. Once we get a little cleaner I'll upload into Debian and then PyLucene should percolate through a bunch of Linux distributions.
If you're going to package JCC and PyLucene separately, you should ideally build JCC in shared mode so that more than one jcc-built extension like PyLucene can be used in any give process. This feature is experimental, requires a rather new setuptools to build. The determination of building for this feature is automatically done near the top of JCC's setup.py file, around line 25.
Then, be sure to build PyLucene with --shared to take advantage of this. At runtime, a shared library, libjcc.so, is required for PyLucene to run. Normally, if the LFLAGS are done correctly, all runtime paths are built into to the executables. Andi.. _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
