[cmake-developers] Enabling SSL support by default when building CMake from source

Nils Gladitz nilsgladitz at gmail.com
Thu Aug 9 09:14:45 EDT 2018


On Thu, Aug 9, 2018 at 2:54 PM Craig Scott <craig.scott at crascit.com> wrote:

> When building CMake from source with default options, you typically end up
> without SSL support, even if the necessary libraries (i.e. OpenSSL) are
> available. I've been bitten by that in my earlier days building CMake and
> I've seen others have a similar experience. Is there any reason why this is
> the default behavior, or is it just that the logic hasn't been added to try
> to enable it by default if available?
>

I remember this having changed to some degree here (~3.6):
https://gitlab.kitware.com/cmake/cmake/commit/190a5fdffd8104ad613854bdd563a0a11dd88f63

Nils
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake-developers/attachments/20180809/dc01022f/attachment.html>


More information about the cmake-developers mailing list