public inbox for
 help / color / mirror / Atom feed
From: Dr Andrew John Hughes <>
To: Andrew Haley <>
Cc: Sean Robert McGuffee <>,
	       "" <>
Subject: Re: Compiling Netbeans with GCJ?
Date: Wed, 18 May 2011 19:37:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 19:26 Wed 18 May     , Andrew Haley wrote:
> On 05/18/2011 07:20 PM, Sean Robert McGuffee wrote:
> > Is the Classpath library that gcj uses something that could be updated to
> > have everything Netbeans needs? Netbeans has grown on me in functionality.
> > It's just that it uses like 2 gigs of memory and is often very slow when
> > many files are open. I imagine if there ever were a case for gcj's
> > existence, a non-interpreted version of Netbeans might be it.
> Please don't top-post on the gcc lists.
> Sure, Classpath could be updated to have everything Netbeans needs,
> but it might be a multi-year task; I just don't know.  I also don't
> know if a gcj-compiled version of Netbeans might really be
> faster/smaller than running on OpenJDK.  Probably not.

As a warning, NetBeans is so untested with anything but the Oracle-produced JDK binaries
that it doesn't even seem to play well with OpenJDK:

which is supposed to be mostly the same code.

The first thing to try is to see if it will run with a Classpath-based VM such as gij,
JamVM or CACAO.  It'll be slow, but that will tell you what kind of issues you're going
to hit.

As Andrew implies though, not for the faint-hearted.
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (

Support Free Java!
Contribute to GNU Classpath and IcedTea
PGP Key: F5862A37 (
Fingerprint = EA30 D855 D50F 90CD F54D  0698 0713 C3ED F586 2A37

      reply	other threads:[~2011-05-18 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2011-05-18 18:27 ` Andrew Haley
2011-05-18 19:37   ` Dr Andrew John Hughes [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).