Yes, change the custom.py. But it really depends on which setup is most
common -- I simply put my own setup into SConstruct. Also, it would be
possible to have SConstruct probe the system for the proper location.

Original Message:
-----------------
From: steven yi stevenyi@csounds.com
Date: Wed, 14 Jul 2004 10:46:57 -0700
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4974] RE: CsoundVST: SWIG Version?


Sounds good.  I'll try upgrading SWIG tonight and giving it a go.

BTW: I noticed for my setup I had to change the SConstruct file to point 
to /usr/include/python2.3 instead of /usr/local/include/python2.3 . 
Would it have been the more correct procedure to use custom.py instead 
of modifying SConstruct?

Thanks,
steven

gogins@pipeline.com wrote:
> I think you probably need to upgrade. I seem to recall upgrading my SWIG.
> In general whenever I develop something, I get the latest versions of all
> the tools, so whatever version of SWIG I used is most likely the one that
> was latest when I did the SConstruct file.
> 


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