Recommended version of SWIG for building mapscript

[Daniel Morissette]

I believe Steve is still using 1.3.21 on cvs.gis.umn.edu to package the 
releases, that's probably the only reference if there is one. In a 
discussion on this list earlier in July I think we concluded that for 
5.0 we should look at upgrading to a new version to start including C# 
and Java interfaces in the source package as well. Note that at the time 
we were discussing 4.8.4 vs 5.0 and 4.10 was not in the air yet, but I 
think it's too late to switch SWIG version for the source distribution 
for 4.10 especially if that would result in incompatible interfaces. (I 
was not aware that upgrading SWIG meant incompatible interfaces. That's 
no good!)

I'll let Assefa comment on the version of SWIG used for MS4W.

Daniel


Umberto Nicoletti wrote:
> Devs,
> do we have a recommended swig version?
> 
> I am still using 1.3.21 but that seems not to be what is used to build 
> MS4W.
> Versions of swig greater than 1.3.24 break the java tests because of a
> new way of handling enumerations. There is a quick fix for Java that
> makes newer swig handle enumerations like in 1.3.21, but I fear this
> will break apps of existing MS4W users.
> 
> Maybe we should decide to adopt a common version on swig to avoid
> these kind of issues in the future?
> 
> Umberto
> 


-- 
Daniel Morissette
http://www.mapgears.com/