http://sablevm.org/bugs/show_bug.cgi?id=88
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From [email protected] 2005-01-14 20:29 -------
Yes David, I think we should basically install all binaries (ie. sablevm,
java-sablevm) normally in $prefix/bin, then provide JAVA_HOME-like env.
in $prefix/lib/sablevm. That seems the most natural for a user.
Actually in Debian packages there's always been /usr/lib/sablevm/bin/java
symlink pointing to ../../../bin/java-sablevm (that is /usr/bin/java-sablevm).
Eventually, I'd like to have something like free-java-sdk:
gadek@gadek:~$ find /usr/lib/fjsdk
/usr/lib/fjsdk
/usr/lib/fjsdk/bin
/usr/lib/fjsdk/bin/java
/usr/lib/fjsdk/bin/jar
/usr/lib/fjsdk/bin/java-alt-setup
/usr/lib/fjsdk/bin/serialver
/usr/lib/fjsdk/bin/gjdoc
/usr/lib/fjsdk/bin/javac
/usr/lib/fjsdk/bin/javah
/usr/lib/fjsdk/bin/javap
/usr/lib/fjsdk/bin/ABOUT.txt
/usr/lib/fjsdk/bin/javadoc
/usr/lib/fjsdk/doc
/usr/lib/fjsdk/doc/ABOUT.txt
/usr/lib/fjsdk/lib
/usr/lib/fjsdk/lib/ABOUT.txt
(this is not all, but it'd be a good start)
But this means we have to find a way to distribute sablevm, classpath,
a compiler (jikes?), cp-tools, and everything else, kitchen sink including.
I had an occasion to take a closer look at GCC's build system lately, and
it seems to me I could make a simplified version of what they do, so that
we could give a user "everything" that constitutes a fully working SDK
(with an option of using some of tools, ie. jikes, he already has installed
on his system).
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.