From: "Douglas Schaefer" <dschaefe@ca.ibm.com>
To: jhealy@redhat.com
Cc: cdt-dev@eclipse.org, eclipse@sources.redhat.com, java@gcc.gnu.org
Subject: Re: [cdt-dev] Natively Compiled Eclipse Snapshot Available
Date: Sat, 02 Aug 2003 05:04:00 -0000 [thread overview]
Message-ID: <OF7AB418FA.BA7F7EC5-ON85256D76.001B3FEC-85256D76.001BC485@torolab.ibm.com> (raw)
In-Reply-To: <1059776792.2253.263.camel@to-dhcp20.toronto.redhat.com>
Way cool guys. Congrats on getting this working. I know you guys have
been working hard on it.
I have a question on gcj - can it handle the use of AspectJ? I have heard
that AspectJ does some wacky stuff at class load time. Aspect oriented
programming may be one solution to our "pulling the parser in too many
directions" problem in the CDT.
Thanks,
Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa, Ontario, Canada
John Healy <jhealy@redhat.com>
Sent by: cdt-dev-admin@eclipse.org
08/01/2003 06:26 PM
Please respond to
cdt-dev@eclipse.org
To
eclipse-dev@eclipse.org, cdt-dev@eclipse.org, java@gcc.gnu.org,
eclipse@sources.redhat.com
cc
Subject
[cdt-dev] Natively Compiled Eclipse Snapshot Available
For quite some time now we've been working on a natively compiled (using
gcj) version of Eclipse. We've made a snapshot available for all to see
at:
http://people.redhat.com/~jhealy/eclipse
On that page you'll find links to the RPM, the SRPM, the dependencies
and to a new mailing list we've created.
We encourage you to join the mailing list for discussion and to report
any problems you find. Instructions for reporting bugs are on the web
page.
Enjoy,
John
--
John Healy <jhealy@redhat.com>
Manager, Product Tools
Red Hat
416-482-2661 x227
_______________________________________________
cdt-dev mailing list
cdt-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/cdt-dev
prev parent reply other threads:[~2003-08-02 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 22:26 John Healy
2003-08-02 5:04 ` Douglas Schaefer [this message]
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=OF7AB418FA.BA7F7EC5-ON85256D76.001B3FEC-85256D76.001BC485@torolab.ibm.com \
--to=dschaefe@ca.ibm.com \
--cc=cdt-dev@eclipse.org \
--cc=eclipse@sources.redhat.com \
--cc=java@gcc.gnu.org \
--cc=jhealy@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).