Our image registration toolkit elastix is being built with a specific tagged version of ITK5 (actually v5.0.0), at https://dev.azure.com/kaspermarstal/Elastix/_build/results?buildId=458
As you see, a Windows build of elastix takes more than an hour, and more that 20 minutes thereof comes from generating (by CMake) and building ITK.
Do you have a suggestion how to avoid rebuilding ITK with each elastix build at the CI?
I did have a look at https://github.com/microsoft/azure-pipelines-artifact-caching-tasks but I don’t yet fully understand how to adjust our azure-pipeline yml file to get it working! Do you?
Another option could be to use prebuilt ITK binaries. Are these available already somewhere, at a location where accessible by azure CI?