RE: non-cygwin X-server

[Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>]

 My goal is to keep XFree86 Cygwin dependent.  It has a lot of pluses
for non-Cygwin folks we alrady have win32-x11 project witha functional
Xserver and all the libraries for MSVC.  A few moments ago I uploaded the
latest version fo win32-x11 server which now has all the 16 extensions,
including GLX and SGI-GLX, and multi-buffering.  It was a pain to build
those with MSVC.  But iit is done.  in comming weeks. SGI (not M$) GLX
dependent OpenGL and GLu libraries as DLLs should be comming.

Because I had been lazy right now and want to go and sleep, I am going to CC
this mail to win32-x11 list members, as an announcemet for the new Xserver
binaries.

Suhaib

BTW you cannot simply build X without Cygwin and have libraries with Cygwin
support.  X needs Xau and Xdmcp, and few others from /xc/lib to resolve tons
of symbols.  That means you will need all the libs in xc//lib without Cygwin
support... that will be chnaging the nature of the project and running
Win32-X11 with another name as Cygwin/XFree.

Suhaib

-----Original Message-----
From: Christopher Faylor
To: 'Cygx (E-mail)'
Sent: 4/10/2001 7:20 PM
Subject: Re: Possibly incorrect explanation of how WaitForSomething works
(and how to fix it) [RC and CGF please comment]

On Tue, Apr 10, 2001 at 03:12:26PM -0400, Harold Hunt wrote:
>> I thought cygwin had fd support for keyboard and mouse? If it
doesn't,
>> then my suggestion would be: write it.
>
>> Just to be difficult: why not pthreads? mutex's, condition variables,
>> thread specific data, limited scheduling (soon to be much
>> more) are all
>> present in snapshots at the moment.
>
>Hmm... I didn't think of that because my idea is to make the X/Server
>independent of Cygwin, so that it can be installed easily and without
>worrying about duplicate copies of cygwin1.dll, etc.  However, I want
to
>keep the XLibs dependent upon Cygwin so that local clients will require
>minimal porting, if any.
>
>Thus, my development efforts have centered around using only Win32 API
>calls.  I haven't written a function yet that make a Cygwin API call.

Ouch.  I wasn't aware of this.  Does this project actually belong in
the win32-x11 domain, then?  Are you using CreateFile instead of fopen,
ReadFile instead of read(), etc?  If so, that means that all of the
cygwin mount table and other directory handling will be bypassed.

It really can't be called a cygwin project if this is the case.

>In any case, everything you suggested was stuff I hadn't thought of,
and
>some of your suggestions were things that I hadn't even known existed
>(/dev/keyboard, etc.); knowing about these things will probably come in
>handy in the future should I do some *nix system-level programming or
if I
>give up on my idea of making the X/Server independent of Cygwin :)

I missed the /dev/keyboard suggestion.  That isn't a cygwin device,
fwiw.

cgf