CMake/MSVC Support

Will Bowers wbowers314 at gmail.com
Fri Jul 19 09:48:34 PDT 2024


Hi again all, thanks for all the additional info.

Greg, I hear you loud and clear. I am not trying to tell you to switch off
your current build pipeline, I just want to see CMake supported as well.
Maybe that support needs to be unofficial, and I am okay with that. I am of
the opinion that PostGIS should build with all major compilers though, so I
would love to help get it building on MSVC (with any build system).

Sandro, I am definitely confused here. But if the lwgeom that builds into
PostGIS is not a fork, why is there an liblwgeom folder with all the source
files in the postgis repo? Why build it as part of PostGIS instead of
simply linking against it as you do with other libraries?

Will

On Thu, Jul 18, 2024, 5:17 PM Greg Troxel <gdt at lexort.com> wrote:

> Will Bowers <wbowers314 at gmail.com> writes:
>
> > Thanks for the info. Like anyone else, I have personal opinions about
> CMake
> > and Meson, but those aren't terribly important right now. There are some
>
> I have some historical info in a broad brush way.   There have been a
> lot of projects that use autoconf/automake and people show up and say
> "cmake is better!  Let's switch!".  There is a "but we have to have no
> regressions from current behavior" and the cmake people agree, and then
> cmake support appears and it has regressions.  Typically they are in
> cross build support and in working on platforms the authors haven't
> tested on because at least for those implementations, they lacked the
> "feature tests only, do not ever  check for a specific OS rule".
>
> So my view, which doesn't officially count, is that to be merged any
> cmake support must be:
>
>   as free of "ifdef FooOS" as the previous system
>
>   capable of building cross, just like autoconf
>
>   support all the --bindir/--libdir stuff that autoconf does
>
>   support proper -R and ld flags like autoconf/libtool does
>
>   support building the code and running tests, with it testing the
>   just-build code *even if there is a previous version installed*.
>
> I think you will find it harder than it seems.
>
> Making small fixes to improve portability is of course a separate
> matter.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20240719/fa80e877/attachment.htm>


More information about the postgis-devel mailing list