[mapserver-dev] Building external projects with libmapserver

[Stephen Woodbridge]

Thomas,

Would it make sense to create a public C-API based on the SWIG interface 
that remains relatively stable and is already documented so the 
incremental effort would be minimal. If this happened, then libmapserver 
would be free to change as needed and third party developers would have 
a stable C-API to work with.

Just a thought.

-Steve

On 9/26/2013 6:29 AM, thomas bonfort wrote:
> Bas,
> The higher level issue we have is that we do not publish a public API,
> and therefore there should be no 3rd party applications having the
> need to link or compile against us. That said, we could rather easily
> bring back the mapserver-config script by having it generated by cmake
> (very closely to the patches you've applied for debian). For 7.0 I
> would like to publish such an API that would be sufficient for
> mapcache, other interested projects can chime in and help if they need
> further functionality exposed.
>
> regards,
> thomas
>
> On 26 September 2013 11:35, Sebastiaan Couwenberg <sebastic at xs4all.nl> wrote:
>> Hi all,
>>
>> Related to the recent threads about building MapCache with MapServer
>> support on mapserver-users [1] and zoo-project on mapserver-dev [2].
>>
>> The mapserver-config executable provided build information that is no
>> longer available in the current CMake builds.
>>
>> While it's possible to build MapCache 1.2.0 with MapServer 6.2.1 by just
>> specifying MAPSERVER_LIBRARY, this is not sufficient to build MapCache
>> 1.2.0 with MapServer 6.4.0.
>>
>> For the Debian packages I've patched the CMake build to export a CMake
>> module which contains among others the list of include directories used
>> to build MapServer so these can be included in the MapCache build.
>> [3][4] This information used to be provided by mapserver-config, but has
>> no equivalent in MapServer 6.4.0.
>>
>> While the exported module looks like a nice solution for CMake based
>> projects, autotools based projects are not able to easily get the list
>> of includes required for MapServer. Or they'd need to parse the CMake
>> module too.
>>
>> Is the CMake module the way to go for external project, or am I missing
>> something?
>>
>> Kind Regards,
>>
>> Bas
>>
>> [1]
>> http://lists.osgeo.org/pipermail/mapserver-users/2013-September/075296.html
>> [2]
>> http://lists.osgeo.org/pipermail/mapserver-dev/2013-September/013654.html
>> [3]
>> http://anonscm.debian.org/gitweb/?p=pkg-grass/mapserver.git;a=blob;f=debian/patches/cmake-mapserver-export.patch;h=2d3bf6c48c8a9da05c7f74e2cf68c4799cc3cd82;hb=HEAD
>> [4]
>> http://anonscm.debian.org/gitweb/?p=pkg-grass/mapcache.git;a=blob;f=debian/patches/cmake-mapserver-include.patch;h=ee74f020fe3bea7360abb34392d8197d91932f51;hb=HEAD
>>
>> --
>> GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>