On Sun, Mar 23, 2008 at 10:46 PM, Andi Vajda <[EMAIL PROTECTED]> wrote: > There are two separate issue here: > - which 'make' utility is used
I got both make (from mingw msys) and nmake (from vc 2003). At this time I could only use make to compile pylucene source since the makefile is created for (unix) make. > - which compiler is used I use standard msi python distribution from the python website which is compiled with vc7 > jcc-PyLucene can of course be built with MSVC since python/distutils/jcc > is actually driving the compilation. Normally, the compiler to use to > compile Python extensions should be the same as the compiler that was used > to build python itself. What compiler that is on Windows depends on what > Python you've installed there. AFAIK, python distributions from python.org is compiled using vc 2003. If jcc use distutils surely it will use vc 2003 to compile the extensions (in this case, pylucene). But if I run the makefile from mingw msys it still uses gcc to compile pylucene. > When 'shared' is enabled when building JCC (see top of setup.py), a > libjcc.dylib on Mac, libjcc.so on Linux and jcc.dll on Windows is build as > well along with the regular jcc python package (along with its _jcc > extension). I see, but then jcc.dll/libjcc.so location would have to be added to the system path/LD_LIBRARY_PATH. > Then, when --shared is used when JCC is invoked, the resulting extension is > linked with this shared library instead of having all the necessary JCC > runtime code statically linked into it. This allows it to share the JCC env > structure with all other such JCC-built extensions. This env structure is > the gateway to the one single Java VM allowed per process. If someone compiled jcc as shared, does the normal jcc as python extension also linked to this shared library (jcc.dll/libjcc.so) otherwise if someone import _jcc and call initvm and at the same time use an extension using shared jcc, two JVM will be created? _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
