Mapscript vs. swig 1.3.26 compilation problems

[szekerest]

1. When compiling mapscript with swigwin 1.3.26 the swig terminates with 
unhandled exception on win32 and segfault on linux.

2. This version of swig generates set accessors for some of the #define 
constants that causes compilation errors for the generated code.

3. This version creates error handler returning a value for a void function 
for the imageObj_getBytes in C#, that causes warnings during compilation.


Most of theese problems are related to a bug in the SWIG parser which will be 
fixed in the upcoming swig 1.3.27.

This version can be downloaded at

http://www.swig.org/swigwin-1.3.27rc1.zip


Problem #3 is due to the followings:

The typemaps for returning gdBuffer in csmodule.i marshal gdBuffer as a void 
return. Due to changes to support value types in C#, any return types must 
specify the value that $null is going to be replaced by, otherwise 0 will be 
used. Unfortunately, it is only void returns that need specifying this, so 
csmodule.i must be changed to

   %typemap(out) gdBuffer
to
   %typemap(out, null="") gdBuffer

so that $null in the SWIG_exception macro gets replaced with the contents of 
the null attribute, ie nothing.

This change maintains the compatibility with SWIG 1.3.25 and 1.3.24 
respectively.


Tamas Szekeres

[szekerest]

swig 1.3.27 is now available and can be downloaded at:

http://prdownloads.sourceforge.net/swig/swig-1.3.27.tar.gz


Tamas Szekeres

[sdlime]

In hopes of keeping the bug list manageable I'm closing this one since it's not 
a MapServer/MapScript problem and a new SWIG version is available.

Steve