public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: "Chu, Casing" <Casing.Chu@space.gc.ca>
Cc: sourcenav@sources.redhat.com
Subject: Re: Compillation of C/C++ parser for SourceNav5.0 under windows
Date: Fri, 11 Jan 2002 18:12:00 -0000	[thread overview]
Message-ID: <20020111162432.05562f05.irox@redhat.com> (raw)
In-Reply-To: <9253F48DBB8FEC4A8CCC376BA61158CCC1F4B9@EXCSTH1.csa.space.gc.ca>


Hi,

On Fri, 11 Jan 2002 17:33:42 -0500 "Chu, Casing" <Casing.Chu@space.gc.ca> wrote:
>
> Hi 
> 
> I recently downloaded the newest version of SourceNavigator (version 5.0)
> and was interested in the C/C++ parsing tool that was used.  The source for
> the C/C++ parsing tool was found //source/snavigator/parsers/cpp from the
> file  SN50-010322-source.tar.qz from the following location :
> http://mirrors.rcn.com/pub/sourceware/sourcenav/releases/ .  My question is
> how would I be able to seperately compile the parser?

some other people are interested in similar things:
  http://sources.redhat.com/ml/sourcenav/2002-q1/msg00025.html

Well, I don't think it would be too hard to build the
parser stand alone.  Start reading the makefile in the parser
directory is probably the best place to start.

> and in addition how would I be able to seperate the parser as a
> stand alone utility?

I don't think the parser would be of much use as a stand alone utility.
You could use the parser with a database and make manual queries
into the database.

Ian.

      reply	other threads:[~2002-01-12  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 16:10 Chu, Casing
2002-01-11 18:12 ` Ian Roxborough [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:
  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=20020111162432.05562f05.irox@redhat.com \
    --to=irox@redhat.com \
    --cc=Casing.Chu@space.gc.ca \
    --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).