Could not find a package configuration file provided by "ITK" (requested
version 4.3) with any of the following names:
ITKConfig.cmake
itk-config.cmake
Could not find a package configuration file provided by "VTK" with any of
the following names:
VTKConfig.cmake
vtk-config.cmake
I was under the impression that superbuild would take care of VTK and ITK dependencies.
In one of the forum posts I found that adding:
set(Slicer_VTK_VERSION_MAJOR 9 CACHE STRING "VTK major version (8 or 9)" FORCE)
mark_as_superbuild(Slicer_VTK_VERSION_MAJOR)
to the CMakeLists.txt solved the issue for the person. It didnt however solve anything for me. Still get the same error.
I tried disabling git ssl verification in the folders. But that did not solve the issue. I am familiar with basic git needed to maintain a repository, but this feels above my level of knowledge.
I do not have a slicer version. But the SHA I am using is 4f3d97c612b417cb8fe1c5688910f71d23a35852 (verified commit from Feb 21st)
I am afraid I am unfamiliar with this. But the command did not return any output.
Yes. I can clone it independently.
I made some progress on my end in the meanwhile. I was able to build VTK project independently in the solution after running the following command git config --global http.sslBackend schannel.
The next error to resolve is from CTK. When I build CTK, this is the error I get.
14> -- Build files have been written to: F:/GP_rel/CTK-build/PythonQt-build
14> No build step for 'PythonQt'
14> Performing install step for 'PythonQt'
14> CMake Error at cmake_install.cmake:43 (file):
14> file INSTALL cannot find
14> "F:/GP_rel/CTK-build/PythonQt-build/Release/PythonQt.dll": No error.
I disabled Slicer_USE_PYTHONQT_WITH_OPENSSL following instructions here, which I don’t think is the issue. I reinstalled Qt with all the components just in case. I am surprised this is giving me issues on Windows, but built without any issues on a Mac along with SlicerIGT extension.
So, this particular error is one that I have been seeing occasionally on windows custom app builds but have not been able to track down the source yet.
Workaround:
In F:/GP_rel/CTK-build/PythonQt-build run this command: cmake --build . --config Release --target PythonQt
What is happening in that the higher level builds are not correctly triggering the PythonQt build for some reason. The cmake command will specifically build that target and then you can try the CTK build again.
Thank you for this.This built CTK. I still have some issues with pip not being found when I do ALL_BUILD. But that’s only affecting the python interactor. I can open the app and read tracking data now.
I believe the cause for a lot of my issues is the workstation being behind a company proxy. Even with admin privileges it is hard to get rid of network issues.
Good to hear. Re: the CTK issue, @jcfr has narrowed it down to a regression with newer CMake version causing PythonQt to not build with the CTK superbuild, so there will be a fix merged for that in the near future.
As a follow up, the commit introducing the regression in CMake has been reverted, a test case has been added, and the original issue has been re-opened.
A Slicer pull-request has also been created to report an error message if an unsupported CMake version is being used. Waiting CMake 3.25.3 is released, consider using 3.24.3.