https://devzone.nordicsemi.com/f/nordic-q-a/3191/a-great-post-in-devzone-blogsI&#39;ve found this great post in devzone blogs, written by RK. I like it and would like to make it better known, both as a point of discussion that as a request to Nordic. -cen-USTelligent Community 13Thu, 28 Aug 2014 02:30:29 GMThttps://devzone.nordicsemi.com/thread/11733?ContentTypeID=1Thu, 28 Aug 2014 02:30:29 GMT137ad170-7792-4731-bb38-c0d22fbe4515:78ca5fff-e029-4c04-bbc3-794141fd3b1cRK<p>Yes - you can use (I do) a build macro, I call it NORDIC_SDK_ROOT. You can add that to a place in the &#39;Windows&#39; environment setting called &#39;Add Filename Replace Macros&#39; which means, when you add an existing file which is within the SDK it adds it relative to that environment variable. When you change the global, it changes the SDK. Rather easy.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/11732?ContentTypeID=1Fri, 15 Aug 2014 17:38:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:96995def-10b7-44e3-921e-8949dd5dbf8cOleh<p>Can you please explain how do you configure different SDK Versions? Is it possible to avoid &quot;add existing source&quot; files, and have the CrossWorks picking up them from SDK Path? thank you!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/11731?ContentTypeID=1Wed, 23 Jul 2014 11:24:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:04ddc56e-5c87-4316-bee6-7d71af3e520eOleh<p>Just discovered the blog link from your post. Great thing imho, I&#39;ll give it a try. Thanks for sharing, I might check blogs more often :)</p><div style="clear:both;"></div>