[mapguide-internals] MapGuide open source builds - Linux & Cmake

Traian Stanev traian.stanev at autodesk.com
Thu Oct 9 10:43:08 EDT 2008

> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-
> internals-bounces at lists.osgeo.org] On Behalf Of Frank Warmerdam
> (External)
> Sent: Thursday, October 09, 2008 10:28 AM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] MapGuide open source builds - Linux &
> Cmake
> Traian Stanev wrote:
> > For what it's worth, I tried to use cmake last night to set up a
> Linux build
> > for the SQLite provider. I wanted to see what the big deal was about
> cmake.
> > Now I know -- it doesn't suck. I see no problem as using cmake for
> the Linux
> > build, or even only as an optional build system alongside automake --
> the
> > cmake files are just some more text files that would be sitting
> alongside
> > the automake files.
> Folks,
> Well, while I'm still a bit uncertain (I have had a very confusing time
> with
> cmake in the QGIS project) I think it could be quite viable as long as
> there
> are long term committed developers like Traian willing to support it.
> If we do move to cmake I would encourage flushing all the
> automake/autoconf
> stuff so that we fully get the advantage of the cmake simplicity.
> (well
> perhaps after a modest transitional period).
> Best regards,
> --
> ---------------------------------------+-------------------------------
> -------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | Geospatial Programmer for Rent
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Hi Frank,

I'm only adding another data point to the discussion, I know you have the opposite opinion. Setting up the cmake files was easier to me than autotools, because I could mentally map the items in the CMakeLists.txt file to items in the project properties of Visual Studio.

I agree with what you said yesterday as well -- we can make the current build link to libraries that are already installed on the system. In fact I think this should have higher priority than switching the build system to cmake, because it would remove the need to compile all the third party components, which has been a big source of compile errors for people who compile on platforms other than RedHat. It would also speed up said build enormously, and would make sure third party components are automatically up to date with the latest bug fixes.

The existing Linux builds systems for both MapGuide and FDO are too opaque and complex and error prone to be tenable in the long run. Simply put, they hurt adoption.


More information about the mapguide-internals mailing list