Newer Swig versions...

[Steve Lime]

Perhaps for the 5.0 release we can consider using the newest version and distributing
pre-swiged bindings for C#, java and ruby. I believe only perl and python are handled
now.

Steve

>>> Tamas Szekeres <szekerest at GMAIL.COM> 7/12/2006 11:07:24 AM >>>
AFAIK the hobu's buildkit is now capable to use even the 1.3.29, and
the previous ms4w was compiled using that kit (with 1.2.37 setting).
The SWIG C# may result in unexpected behaviour when using earlier than 1.3.27.

It must be noted that the SWIG guys like to issue backward
uncompatible releases so continuously supporting the newer versions is
a big deal ;-)

Tamas


2006/7/12, Steve Lime <Steve.Lime at dnr.state.mn.us>:
> There is a 1.3.29 I think.
>
> Steve
>
> >>> thomas bonfort <thomas.bonfort at GMAIL.COM> 7/12/2006 10:50:03 AM >>>
> just my 2c
> latest swig (1.3.28) prevents python mapscript from being properly executed:
> ImportError: ../../build/lib.linux-i686-2.3/_mapscript.so: undefined symbol:
> intarray_setitem
> see also http://trac.gispython.org/projects/PCL/ticket/44 
>
> this is not the case with 1.3.24 (or .27 according to the previous link)
>
> cheers
>
>
>
> On 7/12/06, Daniel Morissette <dmorissette at mapgears.com> wrote:
> >
> > Steve Lime wrote:
> > > Hi all: Currently all distributions comming off cvs.gis.umn.edu 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?
> > >
> > > Steve
> > >
> >
> > I haven't played with SWIG much lately so I do not have an opinion on
> > the upgrade, but I think we should generate the 4.8.4 release before
> > doing the switch just to be safe.
> >
> > BTW, I will prepare the 4.8.4 source for the release later today and
> > will let you know when it's ready to package.
> >
> > Daniel
> > --
> > Daniel Morissette
> > http://www.mapgears.com/ 
> >
>