# Path length limitation in Windows lifted

**URL:** <https://discourse.itk.org/t/path-length-limitation-in-windows-lifted/545>\
**Category:** Engineering\
**Created:** [December 22, 2017, 2:44am UTC](https://discourse.itk.org/t/path-length-limitation-in-windows-lifted/545 "2017-12-22T02:44:32Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![fbudin](https://discourse.itk.org/user_avatar/discourse.itk.org/fbudin/32/14_2.png) [@fbudin](https://discourse.itk.org/u/fbudin)\
**Post date:** [January 3, 2018, 8:33pm UTC](https://discourse.itk.org/t/path-length-limitation-in-windows-lifted/545/15 "2018-01-03T20:33:28Z")

</div>

EDIT: Disabling the tests allowed me to successfully compile ITK with VS2017 and VS2013 (I do not have VS2015 to test)

As a final step, I tried to compile ITK with VS2017 (Windows 10): After reducing the path of the build directory to 69 characters to avoid the error mentioned above:

> [@fbudin](#):
>
> The operation could not be completed. The filename or extension is too long.

I was able to open Visual Studio, start the build, and I now get 5 failures (still due to the path being too long). So I think for now there is no way to work around the 260 characters limitation.

Disclaimer: I did not try any other path sizes than the ones mentioned in my posts (140 and 69).

---

_[View the full topic](https://discourse.itk.org/t/path-length-limitation-in-windows-lifted/545)._