Yaakov S (Cygwin Ports) wrote:
Others have mentioned building *NIX tcl/tk on Cygwin, and I wouldn't
call building gtk2 daunting;
Daunting to build it in such a way that (a) the win32 version doesn't
interfere with the X version, (b) vice versa, and (c) you're SURE that
nothing win32-runtime 'leaks' into either version, but ONLY win32-GUI
gets into the win32 version.
I'm not personally interested, as I'm
focusing on the X11 ports.
What's stopping us from moving the Win32 tcltk in /opt/win32, and making
new *NIX tcl and tk packages in /usr? Then all that's necessary for
insight is to add /opt/win32 to PATH (either through a script,
profile.d, or manually). Similar packages (i.e. that have both X11/*NIX
and Win32 flavors) could use /opt/win32 as well.
All of this mucking about with tk and insight requires the concurrence
of -- and oodles of extra work by -- the tk maintainer and the insight
maintainer. Plus, <speculation alert> given the centrality of the
debugger to the GNUPro product, this sort of change might meet
resistance from the PowersThatBe channeled thru our local Benign
Dictator(s).
Good luck with that.
--
Chuck
