From:	jont AT harlequin DOT co DOT uk (Jon Thackray)
Subject:	cygwin.dll
17 Jan 1997 03:49:54 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<8564.9701171120.cygnus.gnu-win32@dedekind.cam.harlequin.co.uk>
References:	<c=US%a=_%p=E-Stamp%l=MERCURY-970116223207Z-1609 AT mercury DOT e-stamp DOT com>
Original-To:	"'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>
In-Reply-To:	<c=US%a=_%p=E-Stamp%l=MERCURY-970116223207Z-1609@mercury.e-stamp.com>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

James Osburn writes:
 > My two bits on the cygwin.dll and cygnus in general.
 > 
 > First the cygwin.dll is to large It should not 
 > contain the unix to win32 interface. Second, there should
 > be a facility to compile statically and to separate the
 > C runtime and C++ runtimes into seperate dlls and statically
 > linkable libs. The task of porting all the gnu unix to win32
 > via the gcc should be dropped. It poisons an otherwise 
 > very good idea: gcc for win32.

Well I have to disagree with this. Given that I am developing software
for both Win32 and Unix, the fact that many other unix tools are
ported is an excellent and worthwhile objective IMHO. Specifically I
require make (neither Unix nor Win32 provide native makes as good as
gnu make), and therefore sh, and a host of other tools to be called by
make. Strangely, gcc is one of the tools I don't use, although it may
be that it has now improved sufficiently (debugger support, various
bugs fixed, support for MS gratuitous C extensions etc) that I could
now use it.

-- 

Dr. Jon Thackray                jont AT harlqn DOT co DOT uk       44 1223 872522 (voice)
Harlequin Ltd.                                          44 1223 873873 (fax)
Barrington Hall
Barrington
Cambridge CB2 5RG
England
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -