public inbox for
 help / color / mirror / Atom feed
From: Ian Roxborough <>
To: Bruce Korb <>,
Subject: Re: [Fwd: failure notice]
Date: Wed, 07 Nov 2001 08:48:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Bruce Korb wrote:
> Hi Ian,
> That horrid little "ORBZ" disservice has me blocked again.
> has a mail server accepting mail from a mail server
> that accepts mail from an open server, so mine is blocked.
> There are many ways far better than this to filter spam.

Bummer.  But not a lot I can do to correct that, sorry.

> > Subject: How does one add a build rule?
> > To:
> >
> > Hi,
> >
> > The "build rule" tab on the window that pops up
> > from the edit button of the "build settings" window.
> > (This window has no title, so it is hard to name.)
> >
> > Anyway, I seem to be constrained to a half dozen
> > build tools (compilers and linker).  THere is no
> > obvious mechanism for adding more, even from searching
> > the programmer and user guide indexes.  Such is
> > needed.  How?  Thanks! - Bruce

They are two ways:

Either add a "quick rule", there is an example of
this for lex and yacc.  Look for sn_add_simple_ide_rule
in (or sn_prop.cfg if it's installed).

If you are needing something more complex then
you might want to add a "tool chain".  Your best
source of information is to look at the source
code in the "gui" sub directory.  The file is
called toolchain.tcl.  Toolchains are defined
by using the class in toolchain.tcl.

You can find an example of how to define a toolchain
in snavigator/etc/sn_toolchains/gnu-pro-native.

Hope this is of use to you.


       reply	other threads:[~2001-11-28  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2001-11-07  8:48 ` Ian Roxborough [this message]
2001-11-08  3:58   ` Tom Tromey

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).