From: Ian Roxborough <irox@redhat.com>
To: Brad Cox <bcox@virtualschool.edu>, sourcenav@sources.redhat.com
Subject: Re: Using SourceNav for Java
Date: Wed, 28 Feb 2001 14:32:00 -0000 [thread overview]
Message-ID: <200102282229.OAA08438@manx.soma.redhat.com> (raw)
It's been a long time since I touched that code. But IIRC,
I don't think there is a rule for .jar files (zipped up java or class
files, yeah?). It probably won't be hard to add a rule providing
that there is no complexity involved in handling jar files.
My knowedge of java is pretty limited.
Ian.
On Tue, 27 Feb 2001, Brad Cox wrote:
> Date: Tue, 27 Feb 2001 16:53:28 -0500
> To: Mo DeJong <mdejong@redhat.com>, sourcenav@sources.redhat.com
> From: Brad Cox <bcox@virtualschool.edu>
> Subject: Using SourceNav for Java
>
> I've subscribed to this list after trying everything else I could
> think of to get Java compiling via SN and GCJ. Can't seem to make it
> find the core java libraries (java.io.*). I've tried including the
> ..jars as files, as directories, by expanding the jars into
> directories and including the files as files and as directories).
> Nothing works.
>
> How does SN regard jars anyway? As includes? As directories? As
> files? As linker command line options?
>
> Thanks! I'd really appreciate the help.
next reply other threads:[~2001-02-28 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 14:32 Ian Roxborough [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 13:41 source nnavigator on macintosh Mo DeJong
2001-02-27 13:50 ` Using SourceNav for Java Brad Cox
2001-03-01 11:31 ` D-Man
2001-03-01 14:14 ` Brad Cox
2001-03-01 16:09 ` D-Man
2001-03-01 16:51 ` Tom Tromey
2001-03-02 10:36 ` Brad Cox
2001-03-02 11:35 ` Mo DeJong
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=200102282229.OAA08438@manx.soma.redhat.com \
--to=irox@redhat.com \
--cc=bcox@virtualschool.edu \
--cc=sourcenav@sources.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).