Thanks for looking into Mac scons. I would recommend posting again with
somewhat different wording. Have you googled their mailing lists? What
exactly is the problem with pathnames - is this something I might be able
to fix in SConstruct?

Original Message:
-----------------
From: Anthony Kozar anthony.kozar@utoledo.edu
Date: Tue, 06 Apr 2004 02:51:45 -0400
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4450] Re: Csound5


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?


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

The problem cannot be fixed without modifying the guts of Scons.

I wrote tools for the Mac C compiler and linker.  Then, to test I tried
using Scons to build a "hello world" program.  The build script fails long
before it calls any of my code during the initialization of Scons.

Basically, somebody decided to split pathnames at one point using
string.split instead of the functions in os.path and then wrote code
assuming that the path was either for Unix or Windows.  I don't really
understand the purpose of the code (yet), so I can't fix it.

I will try posting on the Scons list again.

Anthony Kozar
anthony.kozar@utoledo.edu


On 4/6/04 10:03 AM, gogins@pipeline.com etched in
stone:

> Thanks for looking into Mac scons. I would recommend posting again with
> somewhat different wording. Have you googled their mailing lists? What
> exactly is the problem with pathnames - is this something I might be able
> to fix in SConstruct?