> 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.
Generating these libraries is quite easy, but the mechanism is dependent on which compiler (gcc or msc) you are using. I don't know how to check for the compiler to set the appropriate link flags. Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
