> > 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. > > If you add it to LFLAGS before building JCC, it'll be there too.
Yes, but this is the wrong place to do it. It means you have to guess what the installed location will be. Better to do it dynamically by JCC itself when stubbing another extension, *after* JCC is installed. > In other words, you need to add another -rpath thingie in there or better > yet, just add the path to libjcc.so in the existing rpath argument, after > another ':'. Yes, but it's just not right to do it manually, when it could be done automatically by the 'install' command. > The config.py file is generated from what you put into > setup.py. (this is done is setup.py itself, by the way) Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
