On Tue, Feb 25, 2003 at 04:24:03PM +0000, David Starks-Browning wrote: > Indeed, the Plucker Team has ignored the possibility to build plucker > on Windows. Who cares? Despite that oversite, it can be done now, > thanks to Cygwin. (That's why Cygwin exists!) Moreover, it's > entirely possible that if header-file-naming was the only impediment > to a Cygwin build, then they might have made the necessary changes. > So I don't think the Plucker Team should be criticized for this issue.
Well, one could probably argue that the Plucker Team has ignored the possibility to build plucker on an OS/390 mainframe. Except for the fact that no one on the plucker team uses OS/390 as a build environment, the need has never come up! :) A question about your solution to fix cygwin. Is it possible to include a check for that in the configure script? Maybe first check if we're using cygwin then check if that environment variable is set.. if not print an error.. That would atleast be useful for anyone else wanting to build under cygwin. -- Adam McDaniel Array.org Calgary, AB, Canada _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
