# Slicer 4.8.1 release and transition to Qt5 and VTK9

**URL:** <https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551>\
**Category:** Development\
**Tags:** qt\
**Created:** [November 28, 2017, 10:57pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551 "2017-11-28T22:57:10Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [November 28, 2017, 10:57pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/1 "2017-11-28T22:57:10Z")

</div>

Hi Slicers,

Next week, I suggest we release Slicer 4.8.1 based of the current master.

Then, we will toggle the default version of Qt, VTK as well as the C++ version to Qt5, VTK9 and C++11.

Let us know what you think.

---

<div class="post-metadata">

**Author:** ![hjmjohnson](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hjmjohnson/32/173_2.png) [@hjmjohnson](https://discourse.slicer.org/u/hjmjohnson)\
**Post date:** [November 29, 2017, 12:02am UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/2 "2017-11-29T00:02:20Z")

</div>

JC,

I am so excited for these changes! I can’t wait for C++11 to be the default. I think that the added checks and extended capabilities of C++11 will make the overall code base much stronger in the long run.

Hans

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 5, 2017, 11:48pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/3 "2017-12-05T23:48:42Z")

</div>

Hi Slicers,

If tomorrow dashboard is green and unless there is any objection, we will release Slicer 4.8.1 based on current master `(*)`.

`(*)` current master: This means cherry-picking all commits since the release onto [slicer/Slicer@master-48](https://github.com/Slicer/Slicer/tree/master-48) branch

---

<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:** [December 6, 2017, 3:52pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/4 "2017-12-06T15:52:45Z")

</div>

VMTK extension packaging on Mac broke by the changes done right after releasing 4.8.0. It means that after 4.8.1 is merged, VMTK will not be available for Mac in 4.8.1. @jcfr Could you have a look and see if you can fix it? See details here: [https://github.com/vmtk/SlicerExtension-VMTK/issues/11](https://github.com/vmtk/SlicerExtension-VMTK/issues/11)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 6, 2017, 3:54pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/5 "2017-12-06T15:54:55Z")

</div>

Most likely related to [r26488](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26488), I will have a look asap.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 15, 2017, 11:55pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/6 "2017-12-15T23:55:28Z")

</div>

> VMTK extension packaging

This is the last outstanding issue. As soon as this is addressed, most likely tomorrow, I will cut the release.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 20, 2017, 3:56am UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/7 "2017-12-20T03:56:20Z")

</div>

Updates:

- The VMTK issue should now be fixed. Changes were specific to the extension. See [PR vmtk/vmtk#209](https://github.com/vmtk/vmtk/pull/209)

- The slicer-4.8 maintenance branch is currently being updated and Slicer 4.8.1 will be tagged shortly.

_all of that from above the Atlantic at 37001 feet (or 11280m)_

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 20, 2017, 5:29am UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/8 "2017-12-20T05:29:14Z")

</div>

Packages for Slicer 4.8.1 are currently being generated.

Once this is complete, the regular nightly builds will start.

Notes:

- At first, packages for Slicer 4.8.1 will not be available on [http://download.slicer.org](http://download.slicer.org). They first have to be marked as released. Also the windows packages will have to be signed.

- Expect some delay, since additional installer are being generated. Extensions build will take a little longer before being available.

- Starting today, extensions for Slicer 4.8.0 will _NOT_ be built anymore. Instead, extensions for Slicer 4.8.1 will be built daily.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 27, 2017, 8:49am UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/9 "2017-12-27T08:49:11Z")

</div>

> The process will be completed in the coming days. Thanks for your patience

Slicer 4.8.1 packages have been marked as released (see [http://slicer.kitware.com/midas3/folder/4989](http://slicer.kitware.com/midas3/folder/4989)) and should show up on [http://download.slicer.org/](http://download.slicer.org/) shortly.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [January 2, 2018, 7:23pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/10 "2018-01-02T19:23:39Z")

</div>

> [@jcfr](#):
>
> Then, we will toggle the default version of Qt, VTK as well as the C++ version to Qt5, VTK9 and C++11.

Are these items below what is still pending before the switch can be flipped?

[https://www.slicer.org/wiki/Documentation/Labs/Qt5-and-VTK8#To\_Do\_List](https://www.slicer.org/wiki/Documentation/Labs/Qt5-and-VTK8#To_Do_List)

---

<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:** [January 3, 2018, 12:42am UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/11 "2018-01-03T00:42:55Z")

</div>

As we have a functional stable release, I think we can afford to have some limitations in nightly releases. I would vote for switching now.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [January 3, 2018, 6:19am UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/12 "2018-01-03T06:19:15Z")

</div>

MacOS and Linux build will be broken. If you can wait few days, we can do  
so during the project week.

Best,  
Jc

---

<div class="post-metadata">

**Author:** ![Davide\_Punzo](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/davide_punzo/32/66104_2.png) [@Davide\_Punzo](https://discourse.slicer.org/u/Davide_Punzo)\
**Post date:** [January 16, 2018, 11:06pm UTC](https://discourse.slicer.org/t/slicer-4-8-1-release-and-transition-to-qt5-and-vtk9/1551/13 "2018-01-16T23:06:30Z")

</div>

Ciao @jcfr, I am just super curious about the state of the transition to Qt5/VTK9 after the project week!