Cygdaemon - planning

Elfyn McBratney
Wed Jul 2 22:38:00 GMT 2003

On Wed, 2 Jul 2003, Nicholas Wourms wrote:

> wrote:
> > On Wed, Jul 02, 2003 at 04:07:12PM +0100, Elfyn McBratney wrote:
> >
> >>Regarding ftok(), IMO that should stay where it is. It's expected to be in the C
> >>library, and there's no need to have it in cygserver now.
> >
> >
> > Right.  Any public facing interfaces have to come from the cygwin DLL.
> >
> > cgf
> I agree and, as I've said before, we should really mirror what glibc
> does in terms of which libraries contain which functions come rather
> then providing lots of silly, non-standard libraries to link against
> which generic configure scripts aren't going to pick up.  Also, how do
> you plan to export the symbols shmat, shmctl, shmdt, shmget?  Currently,
> from when Conrad was working on it, I have them appended to cygwin.din
> so that they are part of the c import library.  I hope the plan isn't to
> use a separate import library...

All interface code, the the various IPC stuff, will stay or be added intermixed
with winsup/cygwin. The interface code will depend on an instance of the server

After Chris does his shirfing of configury hackages I'll start working on
getting that exported. It'd be cool to have this all done for 1.5.1 :-)

> On another note, for consistency's sake (I know they don't do anything),
> shouldn't we move the msg.{cc,h} and sem.{cc,h} as well?

They stay where they are. The utility and functional classes will be in the
winsup/cygserver directory. All interface code (public facing) will be in the C
library (Cygwin), as they are on linux.

> Elfyn, I look forward to testing your changes on WinME as I had been
> doing prior to Conrad's falling off the face of the earth...

Well, I've got a list of stuff that'd be "neat" from cygwin-developers archive,
so my VM will be happy. :-)

> Cheers,
> Nicholas


More information about the Cygwin-developers mailing list