[mapserver-users] problem renaming the mapscript module for perl (swig problem???)

Lime, Steve D (DNR) Steve.Lime at state.mn.us
Tue May 18 11:06:41 EDT 2010


You need to make one more change(s) in plmodule.i. Look for lines of the form:

  mapscript::RFC24_ADD_PARENT_REF(...

and change mapscript to mapscript563. The README in the perl subdirectory talks about this step but the wiki looks to be a bit out-of-date. Here's a great chance to update it!

Steve

-----Original Message-----
From: mapserver-users-bounces at lists.osgeo.org [mailto:mapserver-users-bounces at lists.osgeo.org] On Behalf Of Christian Fritze
Sent: Tuesday, May 18, 2010 5:56 AM
To: mapserver-users at lists.osgeo.org
Subject: [mapserver-users] problem renaming the mapscript module for perl (swig problem???)

Hello everybody!

For evaluation purposes we need to run a mapserver 5.6.3
incl. mapscript for perl in parallel with version 5.0.0
(system is a 64 bit SLES 10 with swig 1.3.27).

So i need to store the mapserver binaries in a separate
directory (no problem of course) and rename the mapscript
module for perl to something like 'mapscript563'.
Following the instructions on
http://trac.osgeo.org/mapserver/wiki/PerlMapScriptBuild35
i did the following:

1. In .../mapserver-5.6.3/mapscript/perl/plmodule.i
   changed the line '%allowexception;' to
   '%feature("allowexcept");' (the former being an alias
   to the latter introduced in swig 1.3.28...)
2. In .../mapserver-5.6.3/mapscript/perl/Makefile.PL
   changed the line "'NAME' => 'mapscript'," to
   "'NAME' => 'mapscript563',"
3. In .../mapserver-5.6.3/mapscript/mapscript.i
   changed the line "%module mapscript" to
   "%module mapscript563"
4. Changed directory to .../mapserver-5.6.3/mapscript/perl/
   and issued:
   swig -shadow -perl5 ../mapscript.i
   rm mapscript.pm
   perl Makefile.PL
   make

So i ended up with files
.../mapserver-5.6.3/mapscript/perl/mapscript563.pm
and
.../mapserver-5.6.3/mapscript/perl/blib/arch/auto/mapscript563/mapscript563.so
which seemed fine at first glance.

However, examining those files shows that not all
function calls in mapscript563.pm got changed from
'mapscript::*' and 'mapscriptc::*' to
'mapscript563::*' and 'mapscript563c::*'

Function calls starting with 'mapscript::' are always calls
to RFC24_ADD_PARENT_REF(...) or RFC24_DEL_PARENT_REF(...)
Function calls starting with 'mapscriptc::' always appear
in subs that call one of mapscript::RFC24_ADD_PARENT_REF(...)
or mapscript::RFC24_DEL_PARENT_REF(...)
Everything else is changed to the intended '563' names.

Is this due to an incomplete interface file for swig?
And will it become a problem after deployment anyway?
(I just test the installation process as such but don't
have access to the applications for actually testing the
functioning of the mapscript module...)

Any help appreciated, thanks in advance...


Christian










_______________________________________________
mapserver-users mailing list
mapserver-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users


More information about the mapserver-users mailing list