public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight Maling List <insight@sources.redhat.com>
Subject: Re: [RFC] Plugins: enhancements
Date: Sun, 25 Nov 2001 11:43:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0111251139420.23851-100000@makita.cygnus.com> (raw)
Message-ID: <20011125114300.pywFVLzYIJVFhaoVwkmlfN_WhjMSpavVou_5S9FSE4w@z> (raw)
In-Reply-To: <87adxbbuak.fsf@creche.redhat.com>

On 24 Nov 2001, Tom Tromey wrote:

> >>>>> "Keith" == Keith Seitz <keiths@cygnus.com> writes:
>
> Keith> Using the following Makefile.in for rhabout, I can now
> Keith> successfully build and install the loadable module "rhabout":
>
> Keith>    include ../Make-rules
>
> This syntax for `include' isn't portable.  Automake has a macro to
> check for a few different include styles.  (Note that you can't be
> guaranteed that there is any include directive, but such systems
> aren't worth worrying about, imnsho.)

I'd love to use automake, but until I can get a clean split between gdb
and Insight's configury, I don't think this is possible. So for now, I am
stuck with using just Makefile.ins.

> Suppose I'm writing a third-party plugin.  How will I find this
> directory to install my files?  I ask because presumably the version
> number is in there anticipating that it will change someday.

Hmmm. Well, I guess there are some solutions... The third-party plugin
writer includes the copy of Make-rules which will tell it where to put it,
we can, as you say, make some sort of script to tell him where to put it,
or he can put it where ever he wants to, and then just tells Insight where
to find it.

I'm also sitting on patches to add an INSIGHT_PLUGINS environment
variable, which will be a colon-separated list of directories to search
for plugins.

Keith


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05  7:09 Keith Seitz
2001-10-05  7:19 ` Tom Tromey
2001-10-05  8:19   ` Keith Seitz [this message]
2001-10-05 10:15     ` Tom Tromey
2001-11-26  9:22       ` Tom Tromey
2001-11-25 11:43     ` Keith Seitz
2001-11-24 15:53   ` Tom Tromey
2001-11-24 14:07 ` Keith Seitz

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=Pine.GSO.4.33.0111251139420.23851-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=tromey@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).