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