From: Brendan Simon <brendan@dgs.monash.edu.au>
To: egcs@cygnus.com
Cc: gdb@sourceware.cygnus.com, insight@sourceware.cygnus.com
Subject: Re: GDB and Insight CVS repositories.
Date: Wed, 18 Aug 1999 18:30:00 -0000 [thread overview]
Message-ID: <37BB5E59.C4BB46BC@dgs.monash.edu.au> (raw)
In-Reply-To: <199908190042.RAA27565@andros.cygnus.com>
Stan Shebs wrote:
> If so, it makes sense to me that there
> is only one master source repository for Insight and GDB. Those that
> don't want a GUI can build with something like "make all-gdb
> install-gdb" and those who want the GUI can build with something like
> "make all install" or "make all-insight install-insight". It seems
> logical to me and can't see why 2 repositories should exist. Maybe this
> is just an interim thing until Insight is officially released.
>
> Makes sense to me too... In fact, in a GDB with Insight configured in,
> the GUI comes up by default if an X display is available, unless you
> say "-nw" (we imitated Emacs behavior).
>
> I guess the other option is to seperate the GUI sources from GDB
> sources. I'm not sure of the details of how this would be done but
> believe it is possible. Are there any technical reasons why this can't
> or shouldn't be done.
>
> It could be done. The main downside to trying to make it a separate
> package is that Insight is linked closely to GDB - it would be
> difficult (though not impossible) to make current Insight sources work
> with vanilla 4.18, for instance. The "easy" separation would be to
> make it a separate source package that you can unpack on top of a GDB
> source tree - would take a few days to figure that one out. The
> "hard" separation would be to make Insight a separate program; that
> would be several months of fulltime work.
From a purist point of view I think it would be better to keep the packages
seperate, regardless of whether Insight is built as a seperate application or
an integrated application. If it is relatively simple to unpack Insight
sources into a seperate sub directory of the GDB source then this sounds like
it would keep RMS happy and keep the GUI repository seperate from the GDB
repository. I guess this is akin to gcc-core, gcc-c++, gcc-fortran, etc
distribution archives. I guess the difference is that all these components
are officialy accepted by GNU.
If this was to happen, would this mean that gdb would require patches ?
Does GDB have an external API (interprocess comms, TCP/UDP sockets) so that
other GUIs could communicate without having to parse CLI output ?
Brendan Simon.
next prev parent reply other threads:[~1999-08-18 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 16:56 Brendan Simon
1999-08-18 17:26 ` Andrew Cagney
1999-08-18 17:42 ` Stan Shebs
1999-08-18 18:30 ` Brendan Simon [this message]
1999-08-18 18:45 ` Andrew Cagney
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=37BB5E59.C4BB46BC@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=egcs@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.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).