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: Resources in natively compiled executables

From: Anthony Green <green at redhat dot com>
To: cbj at gnu dot org
Cc: Tom Tromey <tromey at redhat dot com>, Chris Burdess <dog at bluezoo dot org>, java at gcc dot gnu dot org
Date: Thu, 15 Apr 2004 07:14:17 -0700
Subject: Re: Resources in natively compiled executables
Organization: Red Hat, Inc.
References: <1606C614-8DED-11D8-8F7A-000D934FF4B2@bluezoo.org> <87hdvm4ojj.fsf@fleche.redhat.com> <1081999838.3175.34.camel@lyta.haphazard.org>

On Wed, 2004-04-14 at 20:30, C. Brian Jones wrote:
> Tom does that mean the core: protocol is required to reach what are
> typically classpath visible resources? 

Only for those resources you build into your executable.

>  Doesn't this mean having two
> versions of code to do the same thing?

No, the core protocol handling code is quite unique.

>   Seems like a detail that should
> be hidden to fake the usage expected for getResource(), etc.

I don't think we have to fake anything.  We just put core:/ at the end
of the classpath, and it all magically works.  

AG

-- 
Anthony Green <green@redhat.com>
Red Hat, Inc.

References:
- Resources in natively compiled executables
  - From: Chris Burdess
- Re: Resources in natively compiled executables
  - From: Tom Tromey
- Re: Resources in natively compiled executables
  - From: C. Brian Jones

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