Why is Cygwin1.dll monolithic?

Christopher Faylor cgf-no-personal-reply-please@cygwin.com
Sat Jun 10 17:51:00 GMT 2006


On Sat, Jun 10, 2006 at 12:28:00PM +0200, V??clav Haisman wrote:
>Today I woke up and one of the first things that came on my mind was
>this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?

Maybe you should outline the benefits of such a plan since I can only
see drawbacks.  Both DLLs would have to be loaded by every application
anyway.  That means two separate directory lookups.  And, the "separate
C library" would suffer from dll load-time issues with accessing data
and functions, i.e., it would be slower than the current way of doing
things.  And, then, there would be the "It says cyglibc.dll not found.
Why it not there?" issues that are sure to crop up.

So, other than the esoteric issue of isolating things into separate
regions for maintenance sake, I don't see any end-user benefits.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list