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: "E. Weddington" <ericw at evcohs dot com>
- To: Keith Seitz <keiths at redhat dot com>
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: Fri, 09 Jul 2004 15:12:35 -0600
- Subject: Re: Getting an insight 6.1 executable on Cygwin
- References: <40EEB002.29658.DD97815F@localhost>
On 9 Jul 2004 at 13:56, Keith Seitz wrote:
> On Fri, 2004-07-09 at 13:47, E. Weddington wrote:
>
> > I knew that insight->gdb->cygwin, but is that the only dependency? I'm sorry,
> > I don't know enough about the architecture of Insight.
> >
> > In other words, if gdb could be built without cygwin, then is it true that
> > insight could be built without cygwin?
>
> Yes, that's correct (if we used mingw versions of tcl et al).
>
> > Doing a cygcheck on the the insight executable, I get tcl84.dll depending on
> > cygwin1.dll. I would have thought that this implies that insight, being the
> > tcl/tk part, is directly dependent upon cygwin as well.
>
> Yes, but only because the tcl we use is cygwin-based. If gdb changed, we
> could use a mingw version of tcl.
Ok.... Now I'm confused.
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.
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.)
Thanks for taking the time to answer.
Eric