[pylucene-dev] building PyLucene in script;
diffs between Python 2.5 and 2.4?
janssen at parc.com
Tue Jun 17 10:31:45 PDT 2008
> - The LFLAGS for linux should include -ljvm and -L<dir to libjvm.so>
> I've seen that one some systems (at least Gentoo), failure to include
> on the link line is going to cause it to fail startup because the
> dynamic linker is not going to find the library.
> The same applies for -R/-rpath, it should include the path to libjvm.so.
> The latest JCC setup.py in trunk has that change .
OK, thanks. I'll add that.
> - This "setenv PYTHONPATH ./jcc/build/lib.*/jcc" strikes me as doubly
> . the use of * is probably not going to work as expected if there is
> more than one match
But there won't be; the path that matches will be platform-specific,
created by the build of jcc.
> . setting PYTHONPATH has some specific meaning to Python already, it
> seems that you mean to use it differently here; yes, you are
> unsetting it later, but what if that doesn't happen, for some buggy
> reason ?
Actually, I set PYTHONPATH purposely so that code in the jcc module
can find the submodules it references. I just re-use that variable to
locate the __init__.py file.
More information about the pylucene-dev