On 2006-11-22 22:48+0100 Werner Smekal wrote:
> I managed to make SWIG work with plplot on Windows.
> * I downloaded the latest SWIG for Windows package:
> and unzipped it somewhere.
> * the created folder needs to get into the PATH variable than and the
> lib folder in the CMAKE_INCLUDE_PATH variable, e.g. in my batch files I
> set SWIGDIR=C:\DevZone\swigwin-1.3.29
> set PATH=%SWIGDIR%;%PATH%
> set CMAKE_INCLUDE_PATH=%SWIGDIR%\lib
> cmake is than able to find SWIG and it can be used. I was also
> successful to compile the python bindings.
That's marvelous news.
> but they are still some
> problems running the examples (python 2.4 on windows uses numpy not
> Numeric and so on).
I assume that is NumPy rather than numpy.
There is some confusion over the various names. numpy came out around
python 1.5 but was eventually renamed Numeric, then Old Numeric. Numarray
came out later, but was eventually renamed Old Numarray. Finally, NumPy
came out (version 1.0 just released) which is easy for old-timers to confuse
with the original numpy, but it supersedes all the others I have mentioned.
Once NumPy is adopted by Debian (AFAIK that hasn't occurred yet) and other
leading-edge distros, I would like to change our Numeric code (which started
life as numpy code) over to NumPy. Apparently, that transition is easy to
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project