On Mon, 3 Mar 2008, Bill Janssen wrote:
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 ?
Sorry, this is in the example:
--build # and finally compiling the generated C++ code
# into a Python egg via distutils
oops, I'll change 'distutils' into 'setuptools'
An egg is only built by setuptools which is imported when it is found.
I'm trying a small patch to jcc/python.py, and will report back.
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.
So, how do you recommend bundling a build of PyLucene for distribution?
1. build and bundle setuptools (installing it only when required)
2. build a PyLucene egg with setuptools and bundle it
3. in the distro, make sure that LD_LIBRARY_PATH (Linux) / PATH (Windows)
is set when running your app to reflect different Java installation
locations (not necessary on Mac).
Note that this is probably not enough to account for Java version
differences. This is why we ship a trimmed version of openjdk on Linux and
Windows with Chandler where this is a problem. On Mac, Java is pre-installed.
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
