RE: [Cup-Dev] cygwin

[Craig R. <c-r...@ti...>]

I just did a make -f makefile.w32, but all the ifdefs for
_WIN32 didn't work which, I was under the impression that
cygwin used that same macro.  Course I had to modify all the
shell commands like copy->cp, del->rm.  I can see why this
package is so popular, it's like having a Gnu island inside
a sea of windows!

Craig

  -----Original Message-----
  From: cup...@li...
[mailto:cup...@li...]On
Behalf Of Ke...@AG...
  Sent: Wednesday, July 18, 2001 3:27 PM
  To: cup...@li...
  Subject: RE: [Cup-Dev] cygwin


  You mean in reference to the size of the cygwin package?
Yes, it's quite large. I think though, that those that
really are going to try and 'develop' cup in a windows
environment ought to use cygwin. We will be releasing a
windows binary pre-built, most people don't have to download
cygwin. I think the purpose of having the source
windows-compatible, is for those who want to take the cup
source code, and extend or embed it further on the windows
platform. If that's the case, such a person would need many
development tools ANYWAY, so would be downloading
ming+dozens of seperate tools that are probably just as
large or larger than the single cygwin package.

  But, that's just my 2 cents. :)

  Are you running ./configure and make from the cygwin
environment, or still using the make.bat? make.bat is
useless on cygwin...

  Keith



  -----Original Message-----
  From: Craig Reagan [mailto:c-r...@ti...]
  Sent: Wednesday, July 18, 2001 4:08 PM
  To: Cup-Language-Devel (E-mail)
  Subject: [Cup-Dev] cygwin


  Well I got a build, mine still requires the dll, I'll have
  to get your updates from cvs.

  But man, now I see what they mean by "Minimalist GNU For
  Windows", I won't be doing any full installs over a
dial-up
  connection.

  Craig