# Build and release VMTK via GitHub Actions

**URL:** <https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574>\
**Category:** VMTK\
**Created:** [September 8, 2021, 1:46pm UTC](https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574 "2021-09-08T13:46:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rupertnash](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rupertnash/32/12281_2.png) [@rupertnash](https://discourse.slicer.org/u/rupertnash)\
**Post date:** [September 8, 2021, 1:46pm UTC](https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574/1 "2021-09-08T13:46:52Z")

</div>

For $reasons I need VMTK available for multiple versions of python. So I created a simple Github workflow to build VTK, ITK, and VMTK and bundle up the binaries.

This is here: [https://github.com/hemelb-codes/vmtk-build](https://github.com/hemelb-codes/vmtk-build)

I don’t know if this is of any use to the community? For now, I only need this on Ubuntu, so that’s all I’ve done. If anyone wants other platforms, I’d be happy to accept PRs!

I’d be even happier if you wished to adopt the workflows to run in the main VMTK repo so that everyone can use these.

I’m somewhat cheekily calling the current main branch version 1.4.1-rc1 - apologies for any confusion.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [September 8, 2021, 1:52pm UTC](https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574/2 "2021-09-08T13:52:07Z")

</div>

This is very useful, thank you for sharing. We are still in the process of testing our VMTK builds with VTK9 and ITK5, once we merge them into VMTK master, we’ll revisit continuous integration scripts and may use what you have implemented.

---

<div class="post-metadata">

**Author:** ![rupertnash](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rupertnash/32/12281_2.png) [@rupertnash](https://discourse.slicer.org/u/rupertnash)\
**Post date:** [September 8, 2021, 1:58pm UTC](https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574/3 "2021-09-08T13:58:16Z")

</div>

Yes - looking forward to VTK9 support (we are using that for another program within HemeLB so good to only require a single install). The new vtkPolyData interface is much nicer!

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [September 8, 2021, 3:03pm UTC](https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574/4 "2021-09-08T15:03:22Z")

</div>

If you want to give it a try, the VTK9 build is [here](https://github.com/vmtk/vmtk/pull/372), you can test it and give feedback.

---

<div class="post-metadata">

**Author:** ![rupertnash](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rupertnash/32/12281_2.png) [@rupertnash](https://discourse.slicer.org/u/rupertnash)\
**Post date:** [September 10, 2021, 9:17am UTC](https://discourse.slicer.org/t/build-and-release-vmtk-via-github-actions/19574/5 "2021-09-10T09:17:29Z")

</div>

Thanks - trying a build now: [VTK\_PYTHON\_VERSION must be major version only · hemelb-codes/vmtk-build@5525961 · GitHub](https://github.com/hemelb-codes/vmtk-build/actions/runs/1220650338)