harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arc...@apache.org
Subject svn commit: r368157 - in /incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm: APACHE.README README
Date Wed, 11 Jan 2006 22:56:12 GMT
Author: archie
Date: Wed Jan 11 14:55:56 2006
New Revision: 368157

URL: http://svn.apache.org/viewcvs?rev=368157&view=rev
Update REAME files .. this was meant to be part of r368156.


Modified: incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/APACHE.README
URL: http://svn.apache.org/viewcvs/incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/APACHE.README?rev=368157&r1=368156&r2=368157&view=diff
--- incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/APACHE.README (original)
+++ incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/APACHE.README Wed Jan
11 14:55:56 2006
@@ -15,58 +15,26 @@
 To build JCHEVM, first understand that you have checked out the Subversion
 repository, which is not the same thing as a ready to build distribution
-tarball. To build JCHEVM, a distribution tarball must be created first.
-This causes some files that are required for the build (but not checked
-into the Subversion repository) to be generated. However, once you've
-gone through this process the first time, you will then also be able to
-peform subsequent builds and installs from this, the Subversion-checked-out
-directory (i.e., it's a bit of a bootstrap problem).
+tarball. To build JCHEVM, some files that are part of the distribution and
+required for the build (but not checked into the Subversion repository)
+must be generated first. However, once you've gone through this process
+the first time, you will then also be able to peform subsequent builds
+and installs from this, the Subversion-checked-out directory (i.e.,
+it's a bit of a bootstrap problem).
-To create the distribution tarball and build JCHEVM:
+To make a checked out version of JCHEVM buildable:
-  0. You'll need autoconf, automake, autoheader, and libtool installed first.
+  0. You'll need autoconf, automake, and libtool installed first.
   1. Follow INSTALL step 0 & 1 to install libpopt, libz, and Classpath.
-  2. Run "sh etc/makedist.sh" as root; you may add "--with-classpath=DIR"
-     to specify a non-default Classpath installation directory (the default
-	 is /usr/local/classpath).
-  3. Some root-owned files will be created; you might want to revert to
-     your normal user ownership with "chown -R username ."
-  4. Unpack the resulting tarball jchevm-X.Y.tar.gz and cd into it.
-  5. ./configure && make && make install
+  2. Run "sh etc/regen.sh"; you may add "--with-classpath=DIR" to specify
+     a non-default Classpath install dir (the default is /usr/local/classpath).
+  3. ./configure && make && make install
 The default installation directory is /usr/local (change via --prefix flag
 to configure); on Linux you may need to run "ldconfig /usr/local/lib".
 Alternately, if you can get someone else to build the distribution tarball
-for then you and skip steps 0-3. This of course would be the usual case for
+for then you and skip steps 0-2. This of course would be the usual case for
 average users (rather than developers).
-Here's a posting describing some of the parts of JCVM that may
-be useful to reuse in Harmony:
-    http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200505.mbox/%3c4288F308.9000502@dellroad.org%3e
-Here's how this tarball was created:
-1. cvs -d :ext:yournamehere@cvs.sourceforge.net:/cvsroot/jcvm checkout jcvm
-   When: Sun Sep 25 13:28:25 CDT 2005
-2. Substituted the Apache copyright header (COPYRIGHT.Apache)
-   into all source files.
-3. Removed non-original or irrelevant stuff:
-	java/gnu subdirectory
-	java/java subdirectory
-	soot/ subdirectory
-	website/ subdirectory
-	include/queue.h
-4. Added LICENSE.Apache
--Archie Cobbs

Modified: incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/README
URL: http://svn.apache.org/viewcvs/incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/README?rev=368157&r1=368156&r2=368157&view=diff
--- incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/README (original)
+++ incubator/harmony/enhanced/trunk/sandbox/contribs/jchevm/jchevm/README Wed Jan 11 14:55:56
@@ -1,30 +1,15 @@
-Welcome to JC!
+Welcome to JC Harmony Edition Virtual Machine!
-JC is a Java virtual machine implementation that converts class files
-into C source files using the Soot Java bytecode analysis framework,
-compiles them with GCC, and loads them using a built-in ELF object
-file loader. JC utilizes the GNU Classpath class library and provides
-a fairly complete Java runtime including sophisticated optimizations to
-increase runtime performance. JC also includes a bytecode interpreter,
-and supports execution in either or mixed modes.
+JC Harmony Edition is the Apache Harmony version of the JC Virtual Machine,
+which is described here: http://jcvm.sourceforge.net/
-Although JC has good interpreter performance, JC doesn't try to be
-fast in every situation. Instead, JC focuses on this question: how
-fast can we go if we know some or all of the class files ahead of
-time? The answer is: very fast! Optimizations that are just too
-complex and expensive to perform at runtime are instead performed
-at code generation time. JC's code generator is written in Java,
-using the powerful Soot bytecode analysis framework. When combined
-with the proven power of GCC's C optimizer the results are impressive.
-As an additional benefit, JC contains very little architecture-specific
-code and is highly portable.
+JC Harmony Edition does not perform Java-to-C code generation, currently
+executing only in interpreter mode.
 See INSTALL for installation instructions.
 Once installed, documentation is available via the jc(1) man page
 and the JC manual in info(1), and HTML form under $prefix/share/jc/doc.
-Visit the JC home page at http://jcvm.sourceforge.net/
-$Id: README,v 1.5 2005/05/14 21:42:18 archiecobbs Exp $

View raw message