I did a clean update on Cygwin and Fedora and built and ran Csound 5 without
problem.

I did not do anything about Python version. Should we keep the Python level
"low" or should we assume that anyone who wants to build Csound5 with scons
is probably up to getting the current version?

I have tried to make a -mno-cygwin version of Csound5 and so far I have
failed, nor have I learned much. I am going to try to make a pure mingw
build and/or a Microsoft Visual C++ build - maybe I will learn something
about what is wrong with the Cygwin -mno-cygwin build (it seems to have
something to do with including certain headers both as "C" files and as
"C++" files). This will require modifying SConstruct to take a custom.py
file with paths for dependent libraries, which are not in standard places
for mingw or Windows as reliably as they are on Linux.

This also raises the question of distributing Csound 5 in the Cygwin version
along with the Cygwin DLLs required. I have created in SConstruct a command
to build a zip file containing the required DLLs, which in my opinion are
not too many.

Without giving up on -mno-cygwin or a mingw build, this should make it
possible for people without Cygwin to run Csound5 and CsoundVST on Windows.
Maybe we can start advertising for beta users.

Hi Michael,

I have python 2.2.3 installed on my Fedora computer though will be
upgrading shortly.  However, I'd tentatively say I'd like to stick to
python 2.2 as I think the Sourceforge compile farm for OSX 10.2 only has
python 2.2 (can't check now as there's an outage for unknown reasons
they're looking into). 

As for mingw, I'll try working with that a little more this week.  

Thanks,
steven

 
On Mon, 2004-04-05 at 19:37, Michael Gogins wrote:
> I did a clean update on Cygwin and Fedora and built and ran Csound 5 without
> problem.
> 
> I did not do anything about Python version. Should we keep the Python level
> "low" or should we assume that anyone who wants to build Csound5 with scons
> is probably up to getting the current version?
> 
> I have tried to make a -mno-cygwin version of Csound5 and so far I have
> failed, nor have I learned much. I am going to try to make a pure mingw
> build and/or a Microsoft Visual C++ build - maybe I will learn something
> about what is wrong with the Cygwin -mno-cygwin build (it seems to have
> something to do with including certain headers both as "C" files and as
> "C++" files). This will require modifying SConstruct to take a custom.py
> file with paths for dependent libraries, which are not in standard places
> for mingw or Windows as reliably as they are on Linux.
> 
> This also raises the question of distributing Csound 5 in the Cygwin version
> along with the Cygwin DLLs required. I have created in SConstruct a command
> to build a zip file containing the required DLLs, which in my opinion are
> not too many.
> 
> Without giving up on -mno-cygwin or a mingw build, this should make it
> possible for people without Cygwin to run Csound5 and CsoundVST on Windows.
> Maybe we can start advertising for beta users.
> 
> 

Here is the state for various Mac versions and machines:

OS 9 (Carbon)       MacPython 2.3.3
OS 8-9 (non-Carbon) 2.2.3
System 7 (PowerPC)  not sure (at least 1.5.2)
System 7 (68K)      1.5.2

MacOS X 10.3        MacPython 2.3 installed, difficult to upgrade
OS X 10.2           command-line 2.2 installed, MacPython 2.3.3 available
OS X 10.1           apparently no binary distribution exists (building
                    Unix python from source would probably work)

I only use the non-Carbon version on OS 9, so I am stuck at 2.2.3.  There
may or may not ever be any new releases for OS 9 -- seems to be up in the
air.

Csound currently runs on all PowerPC and 68K Macs running System 7 or later.
And Scons only requires Python 1.5.2, so it is not out of the question to
use it to build Csound on a 68K Mac.

However, I can certainly continue to build Csound without Scons if
necessary.  So, please do whatever you feel is necessary.  The lack of a
decent version of Python for OS X 10.1 users is a little bit disturbing
though.

I did start working on a Mac port of Scons a couple of weeks ago but hit a
snag due to improper platform-neutral handling of path names.  I posted on
the Scons dev list, but no one replied.

Anthony Kozar
anthony.kozar@utoledo.edu


On 4/5/04 10:37 PM, Michael Gogins etched in stone:

> I did not do anything about Python version. Should we keep the Python level
> "low" or should we assume that anyone who wants to build Csound5 with scons
> is probably up to getting the current version?