# Long path using ninja

**URL:** <https://discourse.slicer.org/t/long-path-using-ninja/1702>\
**Category:** Development\
**Created:** [December 21, 2017, 3:08pm UTC](https://discourse.slicer.org/t/long-path-using-ninja/1702 "2017-12-21T15:08:40Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dzenanz](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/dzenanz/32/1992_2.png) [@dzenanz](https://discourse.slicer.org/u/dzenanz)\
**Post date:** [December 22, 2017, 2:42am UTC](https://discourse.slicer.org/t/long-path-using-ninja/1702/6 "2017-12-22T02:42:03Z")

</div>

Trying to build Slicer in a long path build directory, the build fails when it comes turn to configure ITK. Then it snowballs from there. I guess we need to add extra logic to this check to handle the possibility of longer paths which now exists in Windows.

```auto
50> CMake Error at CMakeLists.txt:30 (message):
50> ITK source code directory path length is too long (65 > 50).Please move the
50> ITK source code directory to a directory with a shorter path.
50>
50>
50> -- Configuring incomplete, errors occurred!
50> See also "C:/Dev/Slicer-buildVS2015x64-super-long-path-without-spaces/ITKv4-build/CMakeFiles/CMakeOutput.log".

```

---

_[View the full topic](https://discourse.slicer.org/t/long-path-using-ninja/1702)._
