I created the egg, by hand. To reproduce after running make.. $ cd build $ cp _lucene/_lucene.so lucene
i hand rolled a simple setup.py in the build directory.. # setup.py text from setuptools import setup setup( name = 'lucene', version = '2.3.1', description = ' a Python <http://www.python.org/> extension for accessing Java Lucene <http://lucene.apache.org/java/docs/index.html>.', url = "http://pylucene.osafoundation.org";, author = 'Andi Vajda', author_email = '[EMAIL PROTECTED]', packages = ['lucene'], package_dir = {'lucene': 'lucene'}, package_data = {'lucene': ['*.jar', '*.so'] }, ) # and then setup.py bdist_egg will finish the process. fwiw, i also updated the leopard egg, to the latest pylucene trunk, http://kapil.objectrealms.net/dist cheers, kapil On Mon, Mar 3, 2008 at 9:41 PM, Bill Janssen <[EMAIL PROTECTED]> wrote: > I'd like to package PyLucene as part of the UpLib distribution for OS > X, and I'd like to actually build JCC and PyLucene on my machine, then > put a binary distribution of it into OS X installer. I see that > there's a binary for OS X, built by Kapil Thangavelu, on the Web site, > but I don't see any instructions on how to reproduce that "egg". I > don't see anything in the Makefile, either. What am I missing? > > [Later] Ah, "make compile" generates the egg. May I suggest adding an > alias so that one may say, "make egg"? > > So, if I distribute the PyLucene egg, do I also need to distribute JCC? > Is one egg somehow dependent on the other egg? > > Bill >
_______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
