# VCPKG Support

**URL:** <https://discourse.itk.org/t/vcpkg-support/6334>\
**Category:** Engineering\
**Created:** [December 2, 2023, 6:42pm UTC](https://discourse.itk.org/t/vcpkg-support/6334 "2023-12-02T18:42:01Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)\
**Post date:** [December 2, 2023, 6:42pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/1 "2023-12-02T18:42:02Z")

</div>

Are there plans to support VCPKG with ITK releases, in that will the ITK developers be submitting PRs to the VCPKG repository to update the ITK that is included in VCPKG? The current version is 5.3.0RC2 along with 5.2.1 and 5.2.0.

I see there is a 5.4.0 in the works, is there an estimate on the release date for that?

---

<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:** [December 4, 2023, 2:04pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/2 "2023-12-04T14:04:16Z")

</div>

The planned dates are [listed on GitHub](https://github.com/InsightSoftwareConsortium/ITK/milestones). @matt.mccormick might pitch in with the plan.

---

<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:** [December 4, 2023, 2:09pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/3 "2023-12-04T14:09:31Z")

</div>

We are low on resources, and I don’t think anyone has spare time to keep `vcpkg` up-to-date. Also, a few years ago, when I was submitting pull requests there, they would sit around for weeks before being merged, or even looked at by `vcpkg` developers.

---

<div class="post-metadata">

**Author:** ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)\
**Post date:** [December 4, 2023, 5:55pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/4 "2023-12-04T17:55:37Z")

</div>

I was able to cobble together something that we use for our own vcpkg registry based off of the ITK 5.3.0rc4 VCPKG code. Seems to work for our particular use case. I can work with our registry for it. Happy to share with anyone else that might want to try it out.

> **[GitHub - BlueQuartzSoftware/complex-registry: vcpkg registry for complex](https://github.com/bluequartzsoftware/complex-registry)**
>
> vcpkg registry for complex. Contribute to BlueQuartzSoftware/complex-registry development by creating an account on GitHub.

An up-to-date anaconda package is the most important at this point for us.

---

<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:** [December 4, 2023, 5:57pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/5 "2023-12-04T17:57:08Z")

</div>

@blowekamp Did you maintain the conda package?

---

<div class="post-metadata">

**Author:** ![blowekamp](https://discourse.itk.org/user_avatar/discourse.itk.org/blowekamp/32/79_2.png) [@blowekamp](https://discourse.itk.org/u/blowekamp)\
**Post date:** [December 4, 2023, 6:02pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/6 "2023-12-04T18:02:03Z")

</div>

I do maintain the conga-forge stack for SimpleITK which includes libitk, libsimpleitk, and SimpleITK.

---

<div class="post-metadata">

**Author:** ![matt.mccormick](https://discourse.itk.org/user_avatar/discourse.itk.org/matt.mccormick/32/7_2.png) [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)\
**Post date:** [December 4, 2023, 7:53pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/7 "2023-12-04T19:53:50Z")

</div>

ITK 5.4.0 is coming roughly at the end of this year.

vcpkg has had fairly good support for ITK for quite some time, maintained by the ITK-vcpkg package contributors.

---

<div class="post-metadata">

**Author:** ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)\
**Post date:** [December 5, 2023, 5:58pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/8 "2023-12-05T17:58:28Z")

</div>

The latest working ITK available through VCPKG is 5.2.1.

---

<div class="post-metadata">

**Author:** ![matt.mccormick](https://discourse.itk.org/user_avatar/discourse.itk.org/matt.mccormick/32/7_2.png) [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)\
**Post date:** [December 5, 2023, 6:24pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/9 "2023-12-05T18:24:32Z")

</div>

I see [5.3rc02](https://github.com/microsoft/vcpkg/blob/72010900b7cee36cea77aebb97695095c9358eaf/ports/itk/vcpkg.json#L3).

---

<div class="post-metadata">

**Author:** ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)\
**Post date:** [December 5, 2023, 6:26pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/10 "2023-12-05T18:26:17Z")

</div>

And that is an “RC”. Should I be using that in production?

---

<div class="post-metadata">

**Author:** ![matt.mccormick](https://discourse.itk.org/user_avatar/discourse.itk.org/matt.mccormick/32/7_2.png) [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)\
**Post date:** [December 5, 2023, 6:34pm UTC](https://discourse.itk.org/t/vcpkg-support/6334/11 "2023-12-05T18:34:22Z")

</div>

That is a judgment call for you to make, but the release candidates are generally robust – the code base is mature and well tested. Instability or bugs are more likely to exist in new features, if they are used.