[Chicken-users] Cygwin corner cases

[Brandon J. Van Every]

Brandon J. Van Every wrote:
> Ian Oversby wrote:
>
> > so it is quite conceivable that someone would want to use cygwin for 
> > the build environment but use MinGW for the compiler / libraries 
> > because they want a proper Windows application.  
>
> Well then they're stupid, frankly.  When you build a build, the #1 
> priority is for it to be reliable and work properly.  Mixing and 
> matching Cygwin shells, Cygwin compilers, MinGW compilers, and last 
> but not least, Unix vs. MinGW vs. MSYS CMake generators, is a recipe 
> for disaster.  

It seems I need to distinguish who / what is stupid.  What's stupid, is 
to install a MinGW from www.mingw.org, in its own tree, then install a 
Cygwin shell, and install Cygwin GCC, and expect the MinGW is going to 
work when invoked under Cygwin.  It's also stupid to install a Cygwin 
shell and say you're going to forego Cygwin GCC.  All sorts of stuff in 
Cygwin packages rely on Cygwin GCC, you're probably not going to get 
away with it.

Installing Cygwin only, with Cygwin GCC, and invoking its own "MinGW" 
via -mno-cygwin isn't stupid.  It's just misguided, and an invitation to 
spurious support burdens.


Cheers,
Brandon Van Every