MantisBT - CMake
View Issue Details
0014674CMakeCMakepublic2013-12-30 18:002016-06-10 14:31
Marshall Pierce 
Kitware Robot 
normalminoralways
closedmoved 
AppleMac OS10.9.1
CMake 2.8.12 
 
0014674: SSL support on OS X not working
It seems that CMAKE_USE_OPENSSL is not enabled in the Homebrew and Macports builds of cmake. Thus, the cmake that most Mac-based devs use is going to fail mysteriously (producing a 0-byte file) for URL downloads that use https.

While one could go the route of getting Homebrew, Macports, etc to change their build configs, there's also the issue that openssl is deprecated on OS X anyway, so perhaps OS X builds should default to using Apple's libcurl, which links against the Apple-blessed replacement to openssl.
Use URL in ExternalProject_add with an https:// url.
No tags attached.
Issue History
2013-12-30 18:00Marshall PierceNew Issue
2014-01-02 15:18Brad KingNote Added: 0034900
2016-06-10 14:29Kitware RobotNote Added: 0042456
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0034900)
Brad King   
2014-01-02 15:18   
CMake provides a CMAKE_USE_SYSTEM_CURL option to enable use of the system curl. We expect packagers to enable the use-system-libs options and provide all the dependencies through their packaging tools. If they provide openssl then they should enable CMAKE_USE_OPENSSL too.

However, your suggestion is valid. If CMAKE_USE_SYSTEM_CURL is enabled on OS X we could make that also enable SSL since it is known to work. IIRC the only reason CMAKE_USE_OPENSSL is optional is to avoid requiring users to have OpenSSL just to install CMake to build some code.
(0042456)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.