> >>> Yes, the jcc.dll now builds cleanly. > >> > >> Via setup.py or via your own caring hands ? > > > > setup.py, after I amended the list of platforms to build shared on to > > include "win32". > > Great, I'll check that in.
Well, it's only half the battle. To make it usable, I still need to generate a .LIB file, or a libjcc.a file containing the same things. I see that the Python distribution has c:\Python24\libs\libpython24.a and c:\Python24\libs\python24.lib. I don't know which is actually used when the "-lpython24" switch is passed to g++; I'm guessing it's the libpython24.a file, and that I need to generate a similar libjcc.a file in order to make the --shared build of PyLucene work. MinGW documentation seems to think that foo.lib and libfoo.a have the same structure and content, it's just a difference in how you give them to the linker. Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
