What are the compiler difference between MinGW and cygwin? Source code 
written for the first one is incompatible with the other one? Or there 
is a newer gcc version contained in one of these?

Is a source code compilable (apart the libraries and the 
platform-dependent stuff) by all gcc flavours of the various platforms 
having the same release number?

Now I'm using MinGW-devcpp (that is quite convenient) and (mainly) 
msvc6, i.e. I'm writing code that is compilable by both compilers. Why 
should I pass to cygwin?

Gab

Michael Gogins wrote:
> I'm using Visual Studio .NET (Visual C++ version 7.0) and Dev-C++ (MinGW
> with gcc 3.2). I plan to switch to Cygwin -mno-cygwin with the latest Cygwin
> version of gcc, whatever that is.
> 
> It's conceivable that I'd switch to entirely Linux, if there were something
> like Cool Edit Pro and Cubase SX on Linux. No luck so far, though it's close
> for sound editors what with Ardour and good single-file editors.
> 
> ============================================
> Michael Gogins
> gogins at pipeline period com
> Irreducible Productions
> CsoundVST, an extended version of Csound for programming music and sound
> Available at http://sourceforge.net/projects/csound/
> ============================================
> 
> 
> ----- Original Message ----- 
> From: "steven" 
> To: "Csound Developers Discussion List" 
> Sent: Tuesday, November 25, 2003 8:51 PM
> Subject: [CSOUND-DEV:3519] Re: widgets.cpp
> 
> 
> 
>>I can't verify for older compilers as I'm using gcc 3.3 as well.
>>
>>BTW: Are you using John R's autobuild system or Visual Studio?  I'm
>>trying to use
>>
>>autoreconf -i --force
>>aclocal
>>autoconf
>>configure
>>make
>>
>>and get stopped at main.c due to SIGALRM not being defined.
>>
>>This is using Cygwin 3.3.1 on win2k.
>>
>>Looking at the change in widgets.cpp, it looks to look for cygwin but
>>not what version.  This all should probably be done with the
>>autoheader.h/config.h stuff to check if strstream.h or sstream.h exist,
>>then #ifdef them in depending (same with fstream/fstream.h).
>>
>>steven
>>
>>
>>Robert McNulty Junior wrote:
>>
>>
>>>I changed widgets to work with old compilers as well as new.
>>>Could you update and try it to verify, Steven?
>>>I think I got the hang of this.
>>>Bobby
>>>
>>>
>>>
>>
> 
> 


-- 
Gabriel Maldonado
http://csounds.com/maldonado
--

In the module csound, I added the -kb sticky option for winsound.ico,
to inhibit expansion during checkout using the command:

$ cvs admin -kb winsound.ico

All binary data in a CVS repository should use this option.

I also tagged the current release as csound-4_23a1 to match the
version specified in configure.ac.  We should tag releases so previous
source configuration can be reassembled.  The tag should always match
the version number given in configure.ac with periods replaced by
underscore.

The CVS command really used was:

$ sfcvs csound admin -kb winsound.ico

The sfcvs script I use is:

$ cat $HOME/bin/sfcvs
#! /bin/sh
PROJECT="$1"
shift
SITE=sourceforge.net
CVS_RSH=ssh cvs -z3 -d:ext:$LOGNAME@cvs.$PROJECT.$SITE:/cvsroot/$PROJECT "$@" 
$

John