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

**URL:** <https://discourse.itk.org/t/how-to-avoid-rebuilding-itk-by-azure-ci-at-the-github-of-another-project-elastix/2002>\
**Category:** Engineering\
**Created:** [June 28, 2019, 11:13am UTC](https://discourse.itk.org/t/how-to-avoid-rebuilding-itk-by-azure-ci-at-the-github-of-another-project-elastix/2002 "2019-06-28T11:13:16Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![dzenanz](https://discourse.itk.org/user_avatar/discourse.itk.org/dzenanz/32/1093_2.png) [@dzenanz](https://discourse.itk.org/u/dzenanz)\
**Post date:** [July 12, 2019, 2:13pm UTC](https://discourse.itk.org/t/how-to-avoid-rebuilding-itk-by-azure-ci-at-the-github-of-another-project-elastix/2002/12 "2019-07-12T14:13:44Z")

</div>

I don’t think so, but this question is probably better for `vcpkg` people.

---

_[View the full topic](https://discourse.itk.org/t/how-to-avoid-rebuilding-itk-by-azure-ci-at-the-github-of-another-project-elastix/2002)._
