public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Syd Polk <spolk@redhat.com>
Cc: cravero@hornet.am.qub.ac.uk, sourcenav@sources.redhat.com
Subject: Re: Cannot "add files"  in build window
Date: Fri, 02 Feb 2001 11:11:00 -0000	[thread overview]
Message-ID: <3A7B0635.F4EFEF4B@redhat.com> (raw)
In-Reply-To: <4.2.0.58.20010202083019.01a7c520@pop.cygnus.com>

Yeah, Syd is right.

You can't add files to a target if SN doesn't know
what to do with the files.

If you have a fortran compiler you could use the
sn_add_simple_ide_rule to add a quick and dirty
fortran rule (.f), look in etc/sn_prop.cfg for
an example of using sn_add_simple_ide_rule with
lex and yacc.  Once you have added a rule, you
should see it in the Rules tab (in the target editor).

Ian.

Syd Polk wrote:
> 
> At 01:54 PM 2/2/01 +0000, Walter Cravero wrote:
> 
> >Hi,
> >
> >I downloaded and installed snavigator 4.5.2 (first time i am trying it) . I
> >tried to test it but I couldn't add the files of my project (a couple of
> >fortran files .f) from the "project files" field to the "target files"
> >field in
> >the build window. I am probably making some silly mistake.
> >
> >I am using SUSE linux 7.0 in a PIII box. SN  installed without any error
> >message.
> >
> >Any suggestion???
> >
> >Many thanks
> >
> >Walter
> 
> The build system is not currently set up to compile fortran files.
> 
> Syd Polk                spolk@redhat.com
> Engineering Manager     +1 415 777 9810 x 241
> Red Hat, Inc.

      reply	other threads:[~2001-02-02 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-02  7:06 Walter Cravero
2001-02-02  8:31 ` Syd Polk
2001-02-02 11:11   ` 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=3A7B0635.F4EFEF4B@redhat.com \
    --to=irox@redhat.com \
    --cc=cravero@hornet.am.qub.ac.uk \
    --cc=sourcenav@sources.redhat.com \
    --cc=spolk@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).