On Tue, 04 Jan 2005 13:55:32 -0800, Anthony Green <[EMAIL PROTECTED]> wrote: > On Tue, 2005-01-04 at 16:32 -0500, Stuart Ballard wrote: > If you really want to try the latest and greatest compiler from > Eclipse's cvs, you can try this... > > $ cvs co -d:pserver:sources.redhat.com:/cvs/rhug co ecj-for-jhbuild > > configure and make. The make will check out the latest eclipse compiler > sources and build them with gcj for use with fitzsim's jpackage friendly > java-gcj-compat, which you can get here...
Seems that this no longer works because the Eclipse people added a dependency from Signature.java to a file called Util.java, which in turn depends on a bunch of stuff that's *outside* org.eclipse.jdt.core. I was able to hack around this by producing a trimmed down version of Util.java with only the bits needed by Signature. I was working on a Windows system so I did the steps from Makefile.in of ecj-for-jhbuild by hand, but if you or anyone else is interested in updating the ecj-for-jhbuild package you might be interested in the instructions I put together, which I've attached along with some files that they use. These instructions are specifically for building with ikvm, but you can just skip the last few steps and use jar instead of ikvmc... Stuart. -- http://sab39.dev.netreach.com/
How to get ecj to compile with ikvm:
(These instructions haven't been tested in exactly this form; I went down a
bunch of dead ends in between the steps and had some of the file locations
different. Hopefully I didn't screw up the process of putting the steps into
a logical order for these instructions. If I did, sorry.)
1) Make a working folder:
mkdir ecj
cd ecj
2) Check out the sources:
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/home/eclipse co org.eclipse.jdt.core
3) There are some screwy dependencies from the "compiler" module to the
"model" module which in turn pull in a bunch of files from somewhere outside
core. We can fix these by putting them in a separate directory and trimming
them down to remove the unsatisfiable dependencies. "Util.java", attached,
is a trimmed down version of the copy in
model\org\eclipse\jdt\internal\core\util with only the methods that
Signature.java depends on. On linux obviously replace \ with /, and use
mkdir -p to create parent directories in one shot.
mkdir modelhack\org\eclipse\jdt\core
mkdir modelhack\org\eclipse\jdt\internal\core\util
copy org.eclipse.jdt.core\model\org\eclipse\jdt\core\Signature.java
modelhackorg\eclipse\jdt\core
copy [...path\to\]Util.java modelhack\org\eclipse\jdt\internal\core\util
4) Get a list of all the files in the compiler, batch and modelhack folders
with a .java extension
5) Make a build folder and copy all the .properties and .rsc files from the
compiler, batch and model folders into it.
On Windows, the easiest way to do steps 4 and 5 together was to use a
little perl script, attached:
cd org.eclipse.jdt.core
perl [...path\to\]ecjfiles.pl >..\files.lst
On Linux these steps can be done straight in the shell (UNTESTED!):
cd org.eclipse.jdt.core
find ../modelhack -name *.java >../files.lst
find compiler -name *.java >>../files.lst
find batch -name *.java >>../files.lst
mkdir ../build
(cd compiler; tar c `find compiler -name *.properties -o -name *.rsc`) | (cd
../build; tar x)
(cd batch; tar c `find compiler -name *.properties -o -name *.rsc`) | (cd
../build; tar x)
(cd model; tar c `find compiler -name *.properties -o -name *.rsc`) | (cd
../build; tar x)
6) Compile everything (replace jikes with your java compiler of choice):
jikes -classpath "..\build;..\modelhack;compiler;batch;[...path\to\]rt.jar"
-d ..\build @..\files.lst -Xstdout
7) Test it.
a) Can you get a usage message?
cd ..
java -cp build org.eclipse.jdt.internal.compiler.batch.Main
b) Can you compile a simple Java file using 1.5 features?
java -cp build org.eclipse.jdt.internal.compiler.batch.Main -verbose -1.5
Test.java
java -cp . Test
8) Compile it to a .NET exe:
ikvmc -target:exe -out:ecj.exe -main
org.eclipse.jdt.internal.compiler.batch.Main -recurse build
copy [...path\to\]ikvm\bin\*.dll .
Try for another usage message:
ecj
9) Get it an rt.jar:
ikvmstub IKVM.GNU.Classpath.dll
(ignore the warning if there is one)
ren IKVM.GNU.Classpath.jar rt.jar
10) Compile a test program:
ecj -cp rt.jar -verbose -1.5 Test.java
java -cp . Test
Note that my test program used 1.5 language features but none of the generic
aspects of the class library; if it had, the ikvmstub-generated rt.jar
wouldn't have been enough and you'd have to point it to Sun's libraries (or
a build of the Classpath generics branch if you have one).
Note too that ikvm (as of the snapshot I have) can't run the resulting
Test.class because it refuses the 1.5 class format version.
ecjfiles.pl
Description: Binary data
Util.java
Description: Binary data
_______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
