public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: Ian Roxborough <irox@evilpeople.com>, insight@sources.redhat.com
Subject: Re: Tcl/Tk 8.3 upgrade...
Date: Thu, 14 Jun 2001 15:49:00 -0000	[thread overview]
Message-ID: <3B293F80.2CF6F0D6@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0106141531330.27055-100000@makita.cygnus.com>

Keith Seitz wrote:
> 
> On Thu, 14 Jun 2001, Ian Roxborough wrote:
> 
> > I'm finding yet more and more local changes to Tcl to make it play nicely
> > with Insight running from the build directory (the ones for launching
> > Tcl in tclInitScript.h).
> 
> :-(
> 
> > Is anybody going to mind if I install a script at build time to run
> > gdb out of the build directory.  Maybe call it run-insight.sh or something.
> > Everything works other than typing ./gdb in the build directory,
> > I'm not sure if this is worth all the code changes vs. a 7 line
> > shell script.
> 
> I wouldn't like that, to be honest. That would mean I would have to
> install insight before I can debug it... That's not very developer
> friendly. What other problems are you hitting?
> 

Yes, we must run Insight from the build directory.

Also, how would this affect testsuite runs?

Note that if we make insight's own main.c we can add some code to handle these situations.

> > It looks like it would be a good idea to revisit how Insight is
> > being launched, making SN location independant made a lot of things
> > easier (I was noticing that if I rename my install dir Insight doesn't
> > work any more).  But this is probably outside of the scope the Tcl/Tk
> > upgrade.
> 
> I am playing with configury/automake for insight. This will completely rip
> insight out of the gdb directory. Alas, it is very complicated. I will
> need to test this on a great many machines before I can check it in.
> 

Keith,

This will make it forever impossible for us to use any of the target configuration parameters that are set and available under the src/gdb directory hierarchy.

This means that we can only get information by adding a command to read the gdb "arch" stuff (I wonder if that is _all_ the information about targets -- but I guess one can propose and add anything that is missing).

I do have a couple of versions of Insight that cannot go into the main sources because they have some widgets and a few other things that are specific to the target.  We will need to establish the "official" way to test for architecture/target in the insight code.

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  reply	other threads:[~2001-06-14 15:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 13:11 Ian Roxborough
2001-06-12 18:18 ` Keith Seitz
2001-06-12 22:11   ` Ian Roxborough
2001-06-13  8:08   ` Andrew Cagney
2001-06-13  8:12     ` Keith Seitz
2001-06-13 13:06   ` Mo DeJong
2001-06-14  1:30   ` Ian Roxborough
2001-06-14  8:27     ` Keith Seitz
2001-06-14 15:30       ` Ian Roxborough
2001-06-14 15:33         ` Keith Seitz
2001-06-14 15:49           ` Fernando Nasser [this message]
2001-06-14 20:03             ` Ian Roxborough
2001-06-15  6:35               ` Fernando Nasser
2001-06-15 10:59                 ` Ian Roxborough
2001-06-15 11:14                   ` Keith Seitz
2001-06-14 20:17           ` Ian Roxborough
2001-06-14 17:18         ` 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=3B293F80.2CF6F0D6@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=irox@evilpeople.com \
    --cc=keiths@cygnus.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).