https://devzone.nordicsemi.com/f/nordic-q-a/38344/segger-embedded-studio---fails-to-read-imported-relative-file-paths(note - my core problem is that I&#39;m trying to compile a file that&#39;s larger than 32KB, so I can&#39;t use uVision - if there is an easier way to circumvent this then I don&#39;t really care about getting Embedded Studio to work.) So I&#39;ve followed this tutorialen-USTelligent Community 13Mon, 10 Sep 2018 08:01:58 GMThttps://devzone.nordicsemi.com/thread/147940?ContentTypeID=1Mon, 10 Sep 2018 08:01:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:194495ee-5c31-4de8-975e-91c8cbb08550haakonsh<p>I would use an existing SES example project as it already has everything set up correctly and you should only need to include your sources and headers from your Keil project.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/147909?ContentTypeID=1Mon, 10 Sep 2018 00:41:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c9a09acc-4af0-492a-b8ea-89887248aff1RK<p>well there&#39;s three ways to do it depending on how your project is set up. If you are using a project which is located inside the SDK (like all the SDK examples are) you need to add paths relative to the root of the project, ie they&#39;ll all start ../../../ some number of times. But yes you need to work through and add them all. (I always wished the includes were full path includes and not just single named files).&nbsp;</p> <p>If your project is somewhere entirely different then you have to either do what you&#39;re doing, add the full absolute path, or set up a macro variable in SES (I have one called NRF_SDK_ROOT) and add ${NRF_SDK_ROOT}/path/to/file.h. That&#39;s kind of handy because when you change SDKs, often you just need to change the macro variable.&nbsp;</p><div style="clear:both;"></div>