On Thu, Aug 9, 2018 at 2:54 PM Craig Scott <craig.sc...@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
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
