Hi Michael,

I just setup MSys and MinGW on an XP computer and I used:

MinGW-5.1.3.exe
MSYS-1.0.10.exe

1.0.10 I think is actually the latest stable MSYS and 1.0.11 is only a
preview and doesn't have the simplified single-file installer (as far
as I can see).  Installing those two and using scons 0.97 something,
I'm able to compile.  The version of GCC installed from the 5.1.3 of
MinGW was 3.4.2.

I don't use any individual packages from MinGW, just those two
installers, plus I use Bison and Flex from
http://gnuwin32.sourceforge.net/ .  I don't build everything in Csound
though so don't know if this would work for all the parts but it's
working for me to compile the core csound with WinMM driver, Java
interface, FLTK ops, and few other things.

I'd vote for using these two installer packages as it's really easy to
get those two installed.  I remember a long while back (maybe 5
years?) being able to compile csound with Cygwin and -mno-cygwin but
that was removed and we all settled on MinGW at the time. I have no
idea what difficulties there would be in getting things building with
cygwin now though.

steven

On Feb 8, 2008 8:42 PM, Michael Gogins <gogins@pipeline.com> wrote:
> I am preparing to build Csound 5.08 for the Windows installers. But there
> are problems.
>
> In particular, various parts of the MSys/MinGW/scons toolchain are not
> working together with more current versions. The last versions that build
> Csound are 1.0.11/3.4.2/0.96.1. The current versions are 1.0.11/3.4.5/0.97
> something. In addition, gcc 4.1 is apparently in some sort of pre-release
> stage for Windows.
>
> The problems I experience are:
>
> -- gcc 3.4.5 with MSys/Scons will crash with:
>
>     This application has requested the Runtime to terminate it in an unusual
> way.
>     Please contact the application's support team for more information.
>
> -- scons 0.97 something with MSys will not read Python pathnames in
> custom.py, insists on translating them to Windows pathnames that MSys does
> not handle.
>
> Suggestions, anyone? I am interested in the experience and the preferences
> of the other Csound developers. I am considering:
>
> -- Switching back to Cygwin from MSys -- but I am not sure this will work,
> especially since Cygwin has its own Python. Compiling without the Cygwin
> runtime library (-mno-cygwin) presumably takes care of licensing issues (but
> would it really work for the monster Csound?).
>
> -- Creating a Microsoft Visual C++ build system for Windows -- I can get
> scons to run the Microsoft compiler now, and I need to use Visual C++ builds
> of Fluidsynth and PortAudio anyway.
>
> -- Trying to move ahead to MinGW/gcc 4.1.
>
> -- Sticking with the old tools for now -- there is nothing wrong with the
> finished product.
>
> So again, workarounds, suggestions, preferences?
>
> Regards,
> Mike
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net