1a. The Make file echoes "OK" regardless of the presence of a required program: patch - not cool for that to happen.
patch.exe returns an error exit code if a patch has already been applied. Is there another way this could be worked around ?
2. The header files from MinGW have to be found first by gcj, g++ etc, or errors will stop the make. This is true of c++ and java headers. My solution was to take the cygwin include dir out of the build statement - this is not a long term solution. Is this by design? Is there a less intrusive (to the Makefile) solution?
I don't have this problem. I set GCJ_HOME and all seems to work as expected. No edits needed in the Makefile except for what's documented as such.
3. Swig needs to be at most 1.3.23 or else all sorts of java issues stop the make (differences in class files apparently) I suspect this is a wider problem than just PyLucene...
I use SWIG 1.3.22 without any problem. SWIG does not deal with java class files at all. SWIG thinks all of this is C++. What do you mean with 'all sorts of java issues stop the make' ?
4. Libiconv-2.dll is my latest headache - any ideas on where I should put the dll in order for it to get found? I have tried setting the LD_LIBRARY_PATH to the appropriate location, which is in the shell PATH, and I have placed copies of the dll in strategic locations(i.e. places where I know ld has picked up other libs), I was sure the linker would pick it up... no luck.
I have it in $GCJ_HOME/bin and I install it alongside the _PyLucene.pyd DLL.
Thanks!
What version of MinGW are you using and where did you get it from ? How old is your cygwin environment ? What Windows version are you on ?
Andi..
_______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
