# Transition to VTK 8.0

**URL:** <https://discourse.slicer.org/t/transition-to-vtk-8-0/379>\
**Category:** Development\
**Tags:** build, vtk, qt\
**Created:** [May 24, 2017, 7:44pm UTC](https://discourse.slicer.org/t/transition-to-vtk-8-0/379 "2017-05-24T19:44:17Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [November 4, 2017, 3:16pm UTC](https://discourse.slicer.org/t/transition-to-vtk-8-0/379/6 "2017-11-04T15:16:26Z")

</div>

Regarding

> [@Load DSI Studio (\*.trk.gz) or TrackVis (\*.trk) tracks in Slicer](https://discourse.slicer.org/t/load-dsi-studio-trk-gz-or-trackvis-trk-tracks-in-slicer/1356/3):
>
> @jcfr When do we plan to switch to c++11? I have trouble building Cleaver on Linux and Mac without c++11, too.

Actually, it wouldn’t be completely crazy to go straight to C++14…

- Windows: in the past, Visual Studio was always lagging, but we will be requiring MSVC19 (Visual Studio 2015) anyway, [which supports](http://en.cppreference.com/w/cpp/compiler_support) everything in C++14.

- Mac: Clang has supported everything in C++14 for more than two major releases.

- Linux is the wildcard, because of old clusters. However, they are not any worse off than will be with C++11 – they have to use devtoolset or the equivalent anyway.

@pieper @lassoan

---

_[View the full topic](https://discourse.slicer.org/t/transition-to-vtk-8-0/379)._