Craig Scott
2018-08-09 12:54:48 UTC
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?
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?
--
Craig Scott
Melbourne, Australia
https://crascit.com
New book released: Professional CMake: A Practical Guide
<https://crascit.com/professional-cmake/>
Craig Scott
Melbourne, Australia
https://crascit.com
New book released: Professional CMake: A Practical Guide
<https://crascit.com/professional-cmake/>