# SimpleITK install fails on Windows

**URL:** <https://discourse.slicer.org/t/simpleitk-install-fails-on-windows/23373>\
**Category:** Development\
**Created:** [May 11, 2022, 1:22pm UTC](https://discourse.slicer.org/t/simpleitk-install-fails-on-windows/23373 "2022-05-11T13:22:25Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![keri](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/keri/32/11618_2.png) [@keri](https://discourse.slicer.org/u/keri)\
**Post date:** [May 11, 2022, 8:53pm UTC](https://discourse.slicer.org/t/simpleitk-install-fails-on-windows/23373/9 "2022-05-11T20:53:45Z")

</div>

I agree with you

Sometimes to solve my issues I need to modify Slicer’s `External_smth.cmake`.  
In this case I prepare modified by me `External_smth.cmake` (in `SlicerCAT/CMake` dir) and during configuration time I copy this file to `slicersources-src/SuperBuild/External_smth.cmake` thus replacing Slicer’s original file:

```auto
configure_file(
    "${CMAKE_CURRENT_SOURCE_DIR}/CMake/External_VTK.cmake" 
    "${slicersources_SOURCE_DIR}/SuperBuild/External_VTK.cmake" COPYONLY
  )

```

I can’t do this know (I’m sorry) but in the future some of those dirty solutions should be implemented as a PRs (like with HDF5).

**Just in case some of my propositions (for the future):**

1. either build HDF5 as external project or add an opportunity to find HDF5 through HDF5\_ROOT (probably easier to handle HDF5 versions) var (requires to modify VTK and ITK ext projects). Modified [External\_VTK.cmake](https://github.com/tierra-colada/Colada/blob/master/CMake/External_VTK.cmake) and [External\_ITK.cmake](https://github.com/tierra-colada/Colada/blob/master/CMake/External_ITK.cmake)
2. ITK uses Eigen as third party libs. Add `mark_as_superbuild Eigen3_INCLUDE_DIR` to ITK ext project to link to Eigen. Because if some of ext proj also downloads Eigen and these Eigen libs are of different versions then you may face a problem when the compiled lib uses different Eigen libs in the same function for example. It is difficult to trace (I encountered that)
3. `sqlite` is very popular library and it should be built as shared library. It is pretty often that sqlite is a dependency of some project. For now only `python` uses sqlite. Just in case I prepared [shared sqlite project](https://github.com/tierra-colada/sqlite-amalgamation) (probably it could be done a little cleaner but it works) and the modified [External\_sqlite.cmake](https://github.com/tierra-colada/Colada/blob/master/CMake/External_sqlite.cmake). And probably `sqlite` should better be renamed to `SQLite3` as [CMake prefers](https://cmake.org/cmake/help/latest/module/FindSQLite3.html)

---

_[View the full topic](https://discourse.slicer.org/t/simpleitk-install-fails-on-windows/23373)._