From: Mark Wielaard <mark@klomp.org>
To: eclipse@sources.redhat.com
Cc: debian-java@lists.debian.org
Subject: Running native eclipse on Debian (unstable/x86)
Date: Fri, 05 Sep 2003 14:43:00 -0000 [thread overview]
Message-ID: <1062773014.3316.49.camel@elsschot> (raw)
[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]
Hi,
Someone asked how I got native eclipse running on my Debian box and how
to get the JDT (Java Development Tools) and api documentation/code
completion tooltips work out of the box.
The following only explains how to get the needed binaries installed.
For compiling from source you will need a lot more dependencies and I
have only tried compiling from source on a Red Hat system.
You need to make sure that you have a recent Debian unstable
installation (you need glibc-2.3.x).
Then get the following RPMs:
(Is there a more recent snapshot?)
http://people.redhat.com/~jhealy/eclipse/snapshot-20030802-eclipse-2.1.0-12.i386.rpm
ftp://ftp.redhat.com/pub/redhat/linux/beta/taroon/en/as/i386/RedHat/RPMS/libgcc-ssa-3.5ssa-0.20030801.34.i386.rpm
ftp://ftp.redhat.com/pub/redhat/linux/beta/taroon/en/as/i386/RedHat/RPMS/libgcj-ssa-3.5ssa-0.20030801.34.i386.rpm
http://people.redhat.com/~jhealy/eclipse/ lists:
http://ftp.redhat.com/pub/redhat/linux/beta/taroon/en/ws/i386/RedHat/RPMS/libgcj-ssa-3.5ssa-0.20030617.24.i386.rpm
http://ftp.redhat.com/pub/redhat/linux/beta/taroon/en/ws/i386/RedHat/RPMS/libgcc-ssa-3.5ssa-0.20030617.24.i386.rpm
Which don't seem to exist anymore.
Run 'alien' to turn these into:
libgcc-ssa_3.5ssa-1.20030801_i386.deb
libgcj-ssa_3.5ssa-1.20030801_i386.deb
eclipse_2.1.0-13_i386.deb
And install these with dpkg --install
To make the JDT work out of the box you will need to make your
/usr/bin/java binary the following script:
#!/bin/sh
gij-ssa -Dsun.boot.class.path=/usr/share/java/libgcj-3.5-tree-ssa.jar $*
(Note that /usr/bin/java is handled by the alternative system in Debian
so make sure that you know what you are doing when overriding it.)
Then (optionally) if you happen to have to sources of libgcj
(gcc/libjava) available (or GNU Classpath) create a src.zip file with:
$ fastjar cf src.zip gnu java javax org
Copy this src.zip to the root directory (yes, /).
That way you get automatic API tooltip documentation while typing your
program as can be seen at:
http://www.klomp.org/mark/gij_eclipse/code_completion.png
(Actually that is from an older version of gcj, when eclipse only ran
with gij, but the idea is the same.)
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-09-05 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 14:43 Mark Wielaard [this message]
2003-09-05 20:01 ` Tom Tromey
2003-09-17 7:41 ` Christopher Rauh
2003-09-18 9:03 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1062773014.3316.49.camel@elsschot \
--to=mark@klomp.org \
--cc=debian-java@lists.debian.org \
--cc=eclipse@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).