This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Getting an insight 6.1 executable on Cygwin
- From: Keith Seitz <keiths at redhat dot com>
- To: "E. Weddington" <ericw at evcohs dot com>
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: Fri, 09 Jul 2004 14:15:08 -0700
- Subject: Re: Getting an insight 6.1 executable on Cygwin
- References: <40EEB002.29658.DD97815F@localhost> <40EEB5E3.16834.DDAE78EB@localhost>
On Fri, 2004-07-09 at 14:12, E. Weddington wrote:
> If I go and get just the gdb package, it doesn't seem (to me anyway) to require
> tcl. If I get the insight package, then it requires tcl.
Right.
> So why can't insight go ahead and use a mingw version of tcl, even when gdb
> still requires cygwin? I was under the assumption that the tcl/tk part of it
> insight was just for the GUI, which was separate, somehow, from the underlying
> gdb program. But I could be real wrong about this, as everything seems to get
> bundled into one executable and a couple of dlls for tcl and tk.
>
> (I would bet that the answer has something to do with the architecture of
> insight that I don't know about.)
Nope. Cygwin. It's not nice to mix cygwin and msft runtimes. It's bad
juju. Since gdb requires cygwin, we use a cygwin version of tcl. If gdb
did not rely on cygwin, we would use a version of tcl that did not
require cygwin.
:-)
Keith