---
### Author:  [@al-sabr](https://discourse.cmake.org/u/al-sabr)
#### Post date: [January 31, 2021, 3:52pm UTC](https://discourse.cmake.org/t/need-to-find-replace-all-include-with-new-path-which-doesnt-fit-with-old-path/2661/5 "2021-01-31T15:52:25Z")
Here is the compilation log which shows clearly that many sub-targets are created by CMake and that’s why the #include paths have to be all changed…
> **[1\>------ Rebuild All started: Project: ZERO\_CHECK, Configuration: Debug...](https://pastebin.com/e7kraahr)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
---
### Author:  [@dzenanz](https://discourse.cmake.org/u/dzenanz)
#### Post date: [February 1, 2021, 4:55pm UTC](https://discourse.cmake.org/t/need-to-find-replace-all-include-with-new-path-which-doesnt-fit-with-old-path/2661/6 "2021-02-01T16:55:30Z")
I don’t think your approach can work. If you only put part of ITK (part you need) into a [folder in your project](https://github.com/al-sabr/CTK/tree/ctk-blueberry-port-from-mitk/Libs/mbilog), there are always going to be some compile errors. To make that work, you would need to significantly alter ITK, which is harder to do than to properly incorporate it via [ExternalProject\_Add](https://cmake.org/cmake/help/latest/module/ExternalProject.html) or some other common mechanism.
---
### Author:  [@al-sabr](https://discourse.cmake.org/u/al-sabr)
#### Post date: [February 1, 2021, 5:00pm UTC](https://discourse.cmake.org/t/need-to-find-replace-all-include-with-new-path-which-doesnt-fit-with-old-path/2661/7 "2021-02-01T17:00:45Z")
Actually if you look at this folder I was able to extract all the features (which are minimal from ITK) and was able to make almost a full compilation.
> **[al-sabr/CTK](https://github.com/al-sabr/CTK/tree/ctk-blueberry-port-from-mitk/Libs/mbilog)**
>
> A set of common support code for medical imaging, surgical navigation, and related purposes. - al-sabr/CTK
You think that it is not possible? I think my approach is better to learn which part to modularize instead of making things monolith… what do you think?
---
### Author:  [@dzenanz](https://discourse.cmake.org/u/dzenanz)
#### Post date: [February 1, 2021, 5:05pm UTC](https://discourse.cmake.org/t/need-to-find-replace-all-include-with-new-path-which-doesnt-fit-with-old-path/2661/8 "2021-02-01T17:05:50Z")
As ITK incorporates KWSys as part of its source code, `include`'s reflect that in the path. If you don’t put KWSys in the same relative path that ITK expects, than you will most likely need to edit those files to put a different path, or no path, depending on what you set as `include_directories` in CMake code.
---
### Author:  [@al-sabr](https://discourse.cmake.org/u/al-sabr)
#### Post date: [February 1, 2021, 5:22pm UTC](https://discourse.cmake.org/t/need-to-find-replace-all-include-with-new-path-which-doesnt-fit-with-old-path/2661/9 "2021-02-01T17:22:20Z")
As you can see the output of folder structure is the following:
How come that ITK gets the same output but can use simply the #includes and not me?
I would not like to use this kind of file path **#include “src/itksys/SystemTools.hxx”**
How can I remove the src and all the other subfolders in a more elegant way? It is worst with VNL which is **#include \**
I am not as expert as you in CMake that’s why I don’t know which direction I could go to bypass the default folder structure.