I also accept some included by default, that can be disabled with an option. But never silently depending on what is installed. .___ ._ ..._ .. . ._. .___ .. __ . _. . __.. ... .... ._ .__ Entre dos pensamientos racionales hay infinitos pensamientos irracionales.
On Tue, 5 Oct 2021 at 15:11, Greg Troxel <g...@lexort.com> wrote: > > Javier Jimenez Shaw <j...@jimenezshaw.com> writes: > > > How would CMake behave with all those options that are defined depending > on > > what is present on the compiler machine? > > > > IMHO, the libraries included should be independent on what is already > > installed on the compiler machine. The last time something/somebody > > included "zstd" in our compiler machine, and not in the executing > machine, > > and we couldn't run anything. We did not need zstd, but it was there, > > breaking the execution. I know that the solution there is disable it > > "--without-zstd". What I do not like is the lack of definition, because > > what is present on the compiler machine may change. > > I agree that is is best for a build to hard-require what is required and > decline to use things that are not required. I don't think this issue > is any different autoconf vs cmake. >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev