Long time new build

[Pete Mack]

It's been a while since I used gcc on windows. I am now seeing:

$ make -f Makefile.win
gcc -DWINDOWS -static -Iwin/include -Lwin/lib -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -std=c99 -DUSE_PRIVATE_PATHS -Wdeclaration-after-statement -O2 -I. -mno-cygwin -c -o cave.o cave.c
gcc.exe: error: unrecognized command line option '-mno-cygwin'
make: *** [cave.o] Error 1

using Mingw, git bash shell with properly set build path. Any suggestions?

[Nick]

IIRC

$ MINGW=yes make -f Makefile.win

You'll be hearing more from me

[kaypy]

I seem to recall just deleting the -mno-cygwin out of the makefile... but looking at it, yeah it checks for a MINGW environment variable.

Is it possible to automatically distinguish Cygwin from MinGW? Say uname output or something?

Ah. I see the MINGW=yes is documented on the compiling instructions, but the v3.3.0 readme has a bad link... The faq.txt 2d on the github version is still out of date, btw...

[Pete Mack]

Whoops. There are so many places to check. I used the sticky instructions in the development forum. It'd be nice to get that edited with all 11 pages of confusion by saying: USE THE README TO COMPILE.
BTW: I suspect MINGW is the more common config. Very few windows users will use Cygwin.

I seem to recall just deleting the -mno-cygwin out of the makefile... but looking at it, yeah it checks for a MINGW environment variable.

Is it possible to automatically distinguish Cygwin from MinGW? Say uname output or something?

Ah. I see the MINGW=yes is documented on the compiling instructions, but the v3.3.0 readme has a bad link... The faq.txt 2d on the github version is still out of date, btw...