On Thu, Aug 07, 2008 at 10:48:50AM +0200, Corinna Vinschen wrote: >On Aug 4 19:38, Christopher Faylor wrote: >> Does anyone actually use insight on Cygwin? Keith Seitz, the insight >> maintainer, has recently made changes which will allow insight to work >> with a non-special version of tcl/tk rather than the hacked version that >> it had previously been built with. That opens the door to building a >> real version of tcl/tk for cygwin and linking insight to it. >> Unfortunately, I believe that would mean that insight would need to run >> in an X window rather than natively. >> >> The other alternative is to nuke insight entirely. Is anyone really >> relying on it? Since I barely test it when I release gdb, I'd expect >> that there would be problem reports but I don't remember seeing any for >> quite some time. > >Right now, we have tcl and tk libs which are not using the standard >naming convention for Cygwin DLLs. Doesn't that leave room for having >two versions of insight? We could keep the old tcl84.dll and tk84.dll >and a w-insight which is built against that. Plus other older tcl/tk >apps would still run. And we can have new versions of tcl and tk which >use the Cygwin naming convention and are linked against the X lib, plus >a new x-insight.
So I asked if anyone was using insight, suggesting that maybe it should be retired and your counter suggestion is that I should provide two versions of insight and two versions of tcl/tk (one of them hacked) around instead? No thanks. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
