How to avoid rebuilding ITK by azure CI at the GitHub of another project (elastix)?

Niels_Dekker · July 11, 2019, 6:53pm

Thanks @dzenanz! Please check:

github.com/microsoft/vcpkg

ITK portfile support legacy user code by default

microsoft:master ← N-Dekker:patch-1

opened 06:51PM - 11 Jul 19 UTC

N-Dekker

+1 -3

No longer specify `ITK_LEGACY_REMOVE` and `ITK_FUTURE_LEGACY_REMOVE` options fo…r `vcpkg_configure_cmake`. By default, these two flags are `OFF`, for ITK 5.0.0: https://github.com/InsightSoftwareConsortium/ITK/blob/v5.0.0/CMakeLists.txt#L261 This commit will allow legacy ITK user code to build with vcpkg, and it will ease adding vcpkg support to https://github.com/SuperElastix/elastix Dženan Zukić @dzenanz suggested this change: https://discourse.itk.org/t/how-to-avoid-rebuilding-itk-by-azure-ci-at-the-github-of-another-project-elastix/2002/7 CONTROL version bumped as requested by Phil Christensen @Rastaban