From: Keith Seitz <keiths@redhat.com>
To: Jingzhao Ou <jingzhao.ou@gmail.com>
Cc: insight@sources.redhat.com
Subject: Re: Compiling the latest GDB on cygwin
Date: Wed, 17 Aug 2005 23:43:00 -0000 [thread overview]
Message-ID: <4303CB86.2010907@redhat.com> (raw)
In-Reply-To: <b5706cf105081716347d6a6e11@mail.gmail.com>
Jingzhao Ou wrote:
> I want to make some contribution. Currently, Insight ships with its
> own version of tcl/tk. Also, it still relies on libgui. Could you
> comment on the possibilities and the amount of work required if I want
> Insight to build based on the official tcl/tk and to remove its
> dependence of libgui?
We ship insight with standard tcl/tk/itcl. All that is really required
is updating the configure scripts to check for a system version and use
it instead of the supplied ones.
As for libgui, what we need to do is steal whatever we need from that
and dump the rest. I haven't a clue how much insight actually uses, but
it would be an interesting exercise to figure this out, and see what we
can do to stop using whatever remains.
I any case, I don't see a compelling reason to dump whatever is in
libgui unless someone really has some time on his hands. Insight is
currently the only consumer of libgui, and I'm the maintainer, so we can
do whatever we want (or don't want with it).
Keith
next prev parent reply other threads:[~2005-08-17 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 6:39 Jingzhao Ou
2005-08-16 12:03 ` Dave Korn
2005-08-16 20:48 ` Jingzhao Ou
2005-08-17 15:48 ` Dave Korn
2005-08-17 22:21 ` Jingzhao Ou
2005-08-17 23:34 ` Jingzhao Ou
2005-08-17 23:43 ` Keith Seitz [this message]
2005-08-18 5:35 ` Jingzhao Ou
2005-08-18 17:41 ` Keith Seitz
2005-08-18 18:04 ` Jingzhao Ou
2005-08-19 9:22 ` Dave Korn
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=4303CB86.2010907@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=jingzhao.ou@gmail.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).