This looks like you're having trouble with running SWIG itself, not yet
with compiling the results. I think another poster has suggested a fix.
However, when you do get to the compiling stage, I highly recommend that
you use distutils and a setup.py file to compile the extension , it is
by far the easiest way to compile python extensions.
I recently added directions to the SWIG docs. I don't know that they've
made it to the released version, but you can find them in svn here:
http://swig.svn.sourceforge.net/viewvc/*checkout*/swig/trunk/Doc/Manual/Python.html-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4_______________________________________________
Swig-user mailing list
Swig-user@...
https://lists.sourceforge.net/lists/listinfo/swig-user
