On 2011-06-01 20:54, Roman Chyla wrote:
I would build some other binaries and upload them, will you get me
access?
Done: I added you as a committer to
http://code.google.com/a/apache-extras.org/p/pylucene-extra/
I'll try to keep and post detailed logs for each build I do.
I am planning to add some detailed egg building instructions too.
I will also contact the dudes at:
http://code.google.com/p/pylucene-win32-binary/
They are building windows eggs already
But I also need to build JCC and upload them. Note that the
location of the java that was used for the project built will be
hardcoded inside the dynamic library, but I plan to change the header
and set a few standard paths there.
Ah... good point... meaning this is bad... a build would not be java
location independent then?
This would be a major bummer to have the path to java hardcoded in the .so.
You could commit the patches there if you have some?
Building pylucene/jcc is indeed difficult for newcomers.
Indeed too hard imho. A big deterrent. Such that it does likely impair
the project reach, growth and health.
On Wed, Jun 1, 2011 at 10:54 AM, Philippe Ombredanne
<pombreda...@gmail.com> wrote:
Howdy!
I think it is way too hard to build PyLucene for the mere mortals.
Getting eggs is yet another level of difficulties
I created an issue:
https://issues.apache.org/jira/browse/PYLUCENE-10
and started an Apache extra project, releasing a first egg for the Linux
64/Python 2.5.2/Oracle JDK 1.5 combo
http://code.google.com/a/apache-extras.org/p/pylucene-extra/downloads/list
I hope that can help some folks.
--
Cordially
Philippe
philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by Design (tm) - http://www.nexb.com
http://eclipse.org/atf - http://eclipse.org/soc - http://eclipse.org/vep
http://drools.org/ - http://easyeclipse.org - http://phpeclipse.com
