This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Shrinking/stripping libgcj for superfluous "classes"

From: Martin Egholm Nielsen <martin at egholm-nielsen dot dk>
To: java at gcc dot gnu dot org
Date: Mon, 24 May 2004 13:57:00 +0200
Subject: Re: Shrinking/stripping libgcj for superfluous "classes"
References: <c82lc3$vcj$1@sea.gmane.org> <87r7tnavcg.fsf@fleche.redhat.com> <87ekpn2bql.fsf@gnu.org> <m1brkqsexi.fsf@nowhere.com> <878yfu34to.fsf@gnu.org>

Something else that would really help doing this would be some kind
of dependency tracker, that would help resolving what packages
depend on others. Because otherwise it's mostly guessing and
trial-and-error.

Adam> Read the archives.
The entire archive, or do you have something slightly less usless than
that suggestion?

I just saw that an announcement for Dependency Finder on comp.lang.java.softwaretools doing just that: http://depfind.sourceforge.net/

Best regards,
 Martin

References:
- Shrinking/stripping libgcj for superfluous "classes"
  - From: Martin Egholm Nielsen
- Re: Shrinking/stripping libgcj for superfluous "classes"
  - From: Tom Tromey
- Re: Shrinking/stripping libgcj for superfluous "classes"
  - From: Casey Marshall
- Re: Shrinking/stripping libgcj for superfluous "classes"
  - From: Adam Megacz
- Re: Shrinking/stripping libgcj for superfluous "classes"
  - From: Casey Marshall

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]