just my 2c<br>latest swig (1.3.28) prevents python mapscript from being properly executed:<br>ImportError: ../../build/lib.linux-i686-2.3/_mapscript.so: undefined symbol: intarray_setitem<br>see also <a href="http://trac.gispython.org/projects/PCL/ticket/44">
http://trac.gispython.org/projects/PCL/ticket/44</a><br><br>this is not the case with 1.3.24 (or .27 according to the previous link)<br><br>cheers<br><br><br><br><div><span class="gmail_quote">On 7/12/06, <b class="gmail_sendername">
Daniel Morissette</b> <<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Steve Lime wrote:<br>> Hi all: Currently all distributions comming off <a href="http://cvs.gis.umn.edu">cvs.gis.umn.edu</a> are being build with Swig 1.3.21. I'm just wondering what folks think about moving to the latest versions. Has anyone played with MapScript generated by the new version?
<br>><br>> Steve<br>><br><br>I haven't played with SWIG much lately so I do not have an opinion on<br>the upgrade, but I think we should generate the 4.8.4 release before<br>doing the switch just to be safe.<br><br>
BTW, I will prepare the 4.8.4 source for the release later today and<br>will let you know when it's ready to package.<br><br>Daniel<br>--<br>Daniel Morissette<br><a href="http://www.mapgears.com/">http://www.mapgears.com/
</a><br></blockquote></div><br>