For packaging purposes, I'm planning to change jcc/setup.py as follows so that
autobuilders have fewer problems. It means there are a couple extra paths for
the linker / dynamic loader to search, but I don't see this as a big deal.
Q1: I notice that rpath i386/AMD64 don't really match; one talks about client,
the other talks about a server subdirectory. Is this a simple oversight?
Q2: Maybe this should be considered for the office version of setup.py
after all ?
Jeff
===
LFLAGS = {
'darwin': ['-framework', 'JavaVM'],
'linux2': ['-L/usr/lib/jvm/java-6-sun/jre/lib/i386',
'-L/usr/lib/jvm/java-6-sun/jre/lib/amd64',
'-ljava',
('-Wl,-rpath=/usr/lib/jvm/java-6-sun/jre/lib/amd64:'
'/usr/lib/jvm/java-6-sun/jre/lib/amd64/server:'
'/usr/lib/jvm/java-6-sun/jre/lib/i386:'
'/usr/lib/jvm/java-6-sun/jre/lib/i386/client')],
'sunos5': ['-L/usr/jdk/instances/jdk1.6.0/jre/lib/i386', '-ljava',
('-R/usr/jdk/instances/jdk1.6.0/jre/lib/i386:'
'/usr/jdk/instances/jre/lib/i386/client')],
'win32': ['/LIBPATH:o:/Java/jdk1.6.0_02/lib', 'jvm.lib']
}
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
