Error configuring 3D Slicer - CMake does not support the HTTPS protocol

Development
1

Hi, I’m having trouble while trying to configure, and then generate, de 3D Slicer using CMake.

→ 3D Slicer 4.8: from git SlicerGitSVNArchieve, using git checkout to config the right commit where is the tree for the 4.8 version of 3D Slicer.
→ CMake 3.10.3: built from source – Following software installation - How do I install the latest version of cmake from the command line? - Ask Ubuntu Teocci’s A path to install
→ gcc and g++ available: 9.3 and 5.3.1
→ Qt: 4 and 5

The error:
image

I tried to follow this error: This CMake does not support the HTTPS protocol. Ensure that CMake is compiled with CMAKE_USE_OPENSSL enabled. · Issue #4839 · Slicer/Slicer · GitHub, but when I tryed the steps, these were the answers:

→ /path/to/cmake -P /path/to/Slicer/CMake/SlicerCheckCMakeHTTPS.cmake
image

→ update file CMake/SlicerCheckCMakeHTTPS.cmake:
image

→ Replacing https://raw.githubusercontent.com/Slicer/Slicer/master/CMakeLists.txt with https://google.com
image

I couldn’t find a way to fix it

2

Is there a reason you are trying to build Slicer-4.8 instead latest master? We cannot spend much time with helping developers trying to make very old Slicer versions work.

3

Yes, I’m trying to build a program that a lab collegue did for his PhD, in 2018. I have the full code, which is open in github: GitHub - CSIM-Toolkits/MRCardio: 3D Slicer extension that provides a set of modules of segmentation, registration and cardiac images analysis. But I can’t build it, so I started going “back in time” and using older versions of configurations. I thought of changing the ITK version for start, but it implied that I changed the other, in order to work.

4

In this field, 3 years is a long time. Instead of struggling with trying to review an old software stack, trying to nag application and library developers with supporting old code, and in the end producing something that most people cannot use (since nobody uses Slicer-4.8 anymore), I would recommend to skip forward and build the extension with the latest Slicer version. Lots of things have changed in ITK, VTK, Slicer, Python, etc. but you can always get help for updating software to work with latest application/library versions. If you run into any trouble with Slicer we can definitely help here, and probably with most VTK, ITK, Python problems, too.

1 Like
5

Got it. This solution was a long-term plan, to update the extension, but I will change my plans and start working on it. Thanks for the attention @lassoan, for sure I will need more help in the near future :sweat_smile: