> No, not just. These flags are built into JCC so that when it compiles your > extensions it uses them as well. This is in the file called config.py that > is generated and installed with JCC when it is built itself. > > See > /Library/Python/2.5/site-packages/JCC-1.8-py2.5-macosx-10.5-i386.egg/jcc/config.py
But it only contains the following: INCLUDES=['/usr/java/jdk-1.6/include', '/usr/java/jdk-1.6/include/linux'] CFLAGS=['-fno-strict-aliasing'] LFLAGS=['-L/usr/java/jdk-1.6/jre/lib/i386', '-ljava', '-Wl,-rpath=/usr/java/jdk-1.6/jre/lib/i386:/usr/java/jdk-1.6/jre/lib/i386/client'] So there's no pointer that an extension can use to access libjcc.so. The "-rpath" path needs to be longer. Or, you could add the location of libjcc.so dynamically to it when you stub a jar file with JCC. Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
