Re: New Xconq Windows Executable

[Eric McDonald <mcdonald@phy.cmich.edu>]

On Thu, 28 Aug 2003, Juergen Ruehle wrote:

> Eric McDonald writes:

>  > Yes, it does depend on the Cygwin XFree86 X libraries. We would 
>  > then need to have people install the Cygwin XFree86 stuff (which, 
>  > IMO, is much more stable than 2 years ago). And they would 
>  > essentially be playing Unix Xconq in an X display on their Windows 
>  > machine.
> 
> Actually no: the cygwin tk does not depend on X, but it doesn't
> contain the right headers either. 

Ok, I mounted my NTFS partition that has Cygwin.
I looked at tk.h and it says:
#ifndef _XLIB_H
#   ifdef MAC_TCL
#       include <Xlib.h>
#       include <X.h>
#   else
#       include <X11/Xlib.h>
#   endif
#endif
And the only X11/Xlib.h in my entire Cygwin filespace is under 
/usr/X11R6/include, which, of course, is the real thing, not a 
Tcl/Tk imitation.

So, if anyone was to build a Tcl/Tk-based app under this setup 
(and it is a relatively recent and fairly standard one), he/she 
would, in fact, end up depending on the real X11 stuff. From this 
standpoint, any Cygwin app built thusly would be a true X11 client 
in need of a true X11 server.

But, I suppose this a wasted point, since what you prescribe seems 
like a good idea (it also devalues the AS Tcl/Tk in my eyes). 
It would be nice to build Tcl/Tk for Windows natively under 
Cygwin, and then statically link it into Xconq, removing the 
need of Tcl and Tk DLL's and whatnot. I'll look into it. Thanks.

> Also it seems there is still some tweaking of at least win/Makefile.in
> neccessary. it would be nice if somebody could commit something along
> the lines of (one still has to muck with TCLTKLIB, but I see no way to
> autodetect this):

Your patch looks fine. I was going to commit it later this 
evening, but I suppose I should boot into Windows first and 
actually test it.... I'll take care of it soon, but maybe not 
today.

  Thanks,
    Eric