[mapserver-dev] MapServer 8.0 Config File

Steve Lime sdlime at gmail.com
Thu Jul 8 07:43:36 PDT 2021

Hi Seth: I merged mapserver/main into my config branch and updated the
msLoadMap() signature to take a configObj *. It just creates a reference to
an immutable configObj that can be referenced as needed. I also updated
swiginc/map.i to take an optional second parameter. I haven't done anything
with msLoadMapFromString() as yet. I'll have to look at why tests are
failing but IMHO this should be stable enough to start doing some testing
if you wanted.


On Thu, Jul 1, 2021 at 6:10 PM Steve Lime <sdlime at gmail.com> wrote:

> Yes, it’s stable although I haven’t changed function signatures for
> msLoadMap() in the C code so that probably should happen first.
> On Thu, Jul 1, 2021 at 2:07 AM Seth G <sethg at geographika.co.uk> wrote:
>> HI Steve,
>> I think that should be fine for all the MapScripts.
>> The C# ones have a second constructor [1], but this could ignore the
>> configObj, or have it as a third parameter.
>> Is https://github.com/MapServer/MapServer/pull/6303 stable enough to
>> create a SWIG configObj wrapper for testing?
>> Seth
>> [1]
>> https://github.com/MapServer/MapServer/blob/e48c5cb1fadec9b3f78b256e121093715b428c1a/mapscript/swiginc/map.i#L44
>> --
>> web:http://geographika.co.uk
>> twitter: @geographika
>> On Wed, Jun 30, 2021, at 7:54 PM, Steve Lime wrote:
>> Seth: Do you think this could be workable?
>>   $config = new mapscript::configObj('path to config file');
>>   $map = new mapscript::mapObj('my.map', $config);
>> Seems like we could update the MapScript mapObj constructors to take an
>> optional configObj parameter with default of NULL. Destroying a mapObj
>> doesn't destroy the config (it has a longer scope).
>> --Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20210708/f05dd716/attachment.html>

More information about the mapserver-dev mailing list