[gdal-dev] RFC 84: Migrating build systems to CMake

[Greg Troxel]

Even Rouault <even.rouault at spatialys.com> writes:

> For most packaging system, the set of dependencies available at build
> time is fully controlled by the package requirements. We can assume
> that whatever if available is wished to be used, and ideally a plain
> "cmake .." should automatically find what is available. And if the
> packager properly enumerates its build-time and run-time dependencies,
> that should work.

Generally yes, but the main mechanism is constructing include/lib paths
so that #include, -l and pkgconfig files of things that aren't declared
are not found.  So the cmake build ideally would be trying to
include/link to test if libraries are present, similar to how autoconf
does, rather than reaching out to the filesystem directly to look for
specific files.   But if there's a foo=no equivalent to --disable-foo,
it's not that hard.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20211005/c04ac3d8/attachment.sig>