From: cgf AT bbc DOT com (Christopher Faylor) Subject: getopt? 9 Feb 1998 14:42:22 -0800 Message-ID: Reply-To: cygwin32-developers AT cygnus DOT com To: cygwin32-developers AT cygnus DOT com In trying to rebuild the entire winsup directory on Windows 95, I noticed that getopt is included in the .dll now, but it is not exported -- at least in my snapshot. So, I modified cygwin.din to export the appropriate variables, created a new include file (since it seems that the one in /cdk/include was probably not appropriate) and tried to link cygwin.cc again. This time, ld complained about the lack of a getopt_long in the "new" version of getopt. The Berkeley version doesn't have anything like this, since it is, apparently, only an implementation of old-style single character processing getopt. I'm wondering if this minimal getopt will do more harm than good. It seems that every GNU package will have to resort to using the getopt in libiberty to get getopt_long functionality, so maybe keeping getopt in cygwinb19.dll is not a good thing. I'm not sure I understand why GNU getopt can't be included in cygwin, but if it can't be GNU (licensing problems?), I don't think it should be a "lesser" implementation. OTOH, I can make the changes to cygwin.din and getopt.h available if anybody wants them. -- http://www.bbc.com/ cgf AT bbc DOT com "Strange how unreal VMS=>UNIX Solutions Boston Business Computing the real can be."