# set VTK\_LEGACY\_REMOVE off on mun

**URL:** https://discourse.paraview.org/t/set-vtk-legacy-remove-off-on-mun/428
**Category:** Dashboards
**Created:** [August 14, 2018, 10:19am UTC](https://discourse.paraview.org/t/set-vtk-legacy-remove-off-on-mun/428 "2018-08-14T10:19:28Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 14, 2018, 10:19am UTC](https://discourse.paraview.org/t/set-vtk-legacy-remove-off-on-mun/428/1 "2018-08-14T10:19:28Z")

</div>

mun being the buildbot that is used to test the WikiExamples, I think we should set `VTK_LEGACY_REMOVE` to off.

It is needed because :

- WikiExample is a remote module on github, which prevents it to be tested with fork branch like a submodule can be in VTK.
- Any API change will break the build of WikiExamples on mun, even when using VTK\_LEGACY macro
- If mun can’t build, then mun can’t test standard VTK tests