This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: enlightenment & Eterm
Well I can't speak for John Fortin who is currently patiently waiting
for my initial code, but I've hit a time wall recently after my code
spurt on pthreads...
2-3 months is a realistic estimate. The tasks needed are
* Egors daemon needs to be integrated into cygwin
* We have to add ipc object support to the daemon
* implement msg queues (we have shm, and semaphores are essentially a
freebie from windows as is shm).
At this point there's not really enough together to farm out the coding
to folk with more time - other than shm and egors work it's all theory
;]
Once we've got the framework going though perhaps someone from here
would like to jump and help cross-check the code to ensure it works
welll with xfree86?
Rob
----- Original Message -----
From: "Alan Hourihane" <alanh@fairlite.demon.co.uk>
To: <cygwin-xfree@sources.redhat.com>
Sent: Monday, April 30, 2001 7:55 PM
Subject: Re: enlightenment & Eterm
> On Mon, Apr 30, 2001 at 07:42:05PM +1000, Robert Collins wrote:
> > Uhmm no. Theres some discussion on cygwin-dev, and a prototype
cygwin
> > daemon by egor, and some code on my hard drive. Thats it at the
moment.
> >
> > I should add that the in-cygwin code will co-exist with cygipc to
the
> > extant that old binaries linked with cygipc should still work, but
> > a) all new compiles will link against cygwin (the default anyway).
> > b) cygipc and in-cygwin IPC won't interoperate.
> >
> That shouldn't be a problem then. For now, people who need ipc/shm
support
> will need to go get cygipc and build X themselves. The patch makes it
easy
> for us to turn it on/off.
>
> How long do you think before in-cygwin IPC hits maturity ? As with X
maturing
> rapidly on Windows people will start needing it, and thus the only
option
> currently is cygipc.
>
> Alan.
>