On 2013-07-12 11:21+0200 Eric Noulard wrote:
so my best bet is that the CMake command your are using has no SSL support which makes the "https" handling fail with "unsupported protocol".
Hi Eric: Your hypothesis was absolutely correct (as you can see from my later posts in this thread). In fact, the Debian wheezy version of cmake cannot handle my test case, and the only version I got to work was my own build with a particular choice of system curl library. What was the exact version of CMake that you found would pass my download test? By bringing the openssl library build in house (similar to the way there is an in-house version of libcurl), I think CMake could be made a lot less fragile with respect to downloading. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
