Summary: | missing infrastructure for installing the native part of a java package | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Schuster <theBohemian> |
Component: | [OLD] Library | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 31468 |
Description
Robert Schuster
2004-03-07 09:16:32 UTC
We've been revamping the handling of jar files in Gentoo, and this will also require proper attention. This, sadly, is a very time-consuming project:/ We now have a system for this. It's rather simple, and can hopefully remain so. Java ebuilds just use the java-pkg_doso for its .so files. Afterwards, the startup script must add -Djava.library.path=/usr/lib, and it just works(tm). We may need to extend this in the future. And it's somewhat of a hassle for libraries, but we've not been able to figure out working, JDK-independent solution that's transparent. I.e. javac -cp `java-config -p swt-3`:. MySWTApp.java ; java -cp `java-config -p swt-3` MySWTApp would be nice, but for now, java -Djava.library.path=/usr/lib -cp `java-config -p swt-3` MySWTApp |