Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3B36564E.9020907@ece.gatech.edu>
Date:	Sun, 24 Jun 2001 17:06:22 -0400
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607 Netscape6/6.1b1
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	"David A. Cobb" <superbiskit AT home DOT com>
CC:	Max Bowsher <cygwin AT bowshernet DOT freeserve DOT co DOT uk>,
	Cygwin General MailList <cygwin AT cygwin DOT com>
Subject:	Re: RXVT: Launching the root window/login shell
References:	<5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20010620123032 DOT 022e1ec0 AT mail> <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20010622215511 DOT 04905b60 AT mail> <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20010624163421 DOT 06520a40 AT mail>

Ummm...guys.  Did anybody bother to read /usr/doc/Cygwin/rxvt-*.README ? 
  Or search the recent archives concerning rxvt?

Steve O. originally ported rxvt to native windows.  Also, there was an 
existing port of libXpm (which rxvt optionally uses) to Windows.  This 
Xpm port used a "fake" X11 library that (a) worked with the native 
Windows windowing environment (no Xserver required), and (b) provided 
--just enough-- of the Xlib calls to satisfy libXpm.  Steve's initial 
port of rxvt did NOT use libXpm at all (he eliminated all dependency on X).

Okay, so then Steve got clever.  He used the Windows libXpm port's fake 
"X" lib, rewrote parts of it as a wrapper, built his own libXpm that 
used his new "W" lib, and then built a new rxvt that used his new libXpm 
and "W" libs.  When he put all this together, he got an rxvt that
   (a) could run on Native Windows without needing an Xserver
   (b) could also run in "X" mode with an Xserver if desired
This magic was performed by the "W" lib (remember, "W" is Steve's 
modified version of the fake Xlib that came with libXpm).  Depending on 
the value of the DISPLAY variable, "W" uses the fake Xlib calls (and 
thus runs in "native" mode, or "W" uses *real* Xlib calls (and thus runs 
in "X" mode and requires an Xserver.

I probably got a few details wrong, but that's the basic idea.  For more 
infom: use the source, luke.

--Chuck


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -