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: gij and -cp/-classpath

From: Nic Ferrier <nferrier at tapsellferrier dot co dot uk>
To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
Cc: tromey at redhat dot com, Andrew Pinski <pinskia at physics dot uc dot edu>, GCC-Java <java at gcc dot gnu dot org>
Date: 10 Apr 2002 01:58:53 +0100
Subject: Re: gij and -cp/-classpath
References: <E78A8EF7-4BE7-11D6-A8FB-000393122612@physics.uc.edu><87bscsir0z.fsf@creche.redhat.com><87g024v2w2.fsf@pooh-sticks-bridge.tapsellferrier.co.uk><3CB38D93.7020500@waitaki.otago.ac.nz>

Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:

> Yes, the idea is to have one argument parser which can be shared by: 
>  
> - gij command line 
> - vm_args for CNI & JNI invocation API 
> - an environment variable (LIBGCJ_ARGS or some such) which sets VM  
> parameters for any gcj binary 

I don't understand that last part: don't *all* gcj applications have
to use the invocation API? I presumed that GCJ compiled (native) code
was wrapped with some invocation caller.

Nic

Follow-Ups:
- Re: gij and -cp/-classpath
  - From: Bryce McKinlay

References:
- gij and -cp/-classpath
  - From: Andrew Pinski
- Re: gij and -cp/-classpath
  - From: Tom Tromey
- Re: gij and -cp/-classpath
  - From: Nic Ferrier
- Re: gij and -cp/-classpath
  - From: Bryce McKinlay

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