<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How to include dependency files (.h) in nRF5 SDK projects using Segger Studio and GIT</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/60321/how-to-include-dependency-files-h-in-nrf5-sdk-projects-using-segger-studio-and-git</link><description>Hoping this is a simple fix. I&amp;#39;m new to using GIT and I&amp;#39;d like to setup my nRF 5 SDK projects to work with GIT so I can backup and collaborate with others. I have a few nRF projects that I made keeping the same folder structure in the SDK folder. I&amp;#39;m</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 20 Apr 2020 12:50:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/60321/how-to-include-dependency-files-h-in-nrf5-sdk-projects-using-segger-studio-and-git" /><item><title>RE: How to include dependency files (.h) in nRF5 SDK projects using Segger Studio and GIT</title><link>https://devzone.nordicsemi.com/thread/245540?ContentTypeID=1</link><pubDate>Mon, 20 Apr 2020 12:50:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75c26443-56d2-4952-9e6b-8ed62dc70fca</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not aware of any settings in SES that would allow you to import all dependencies automatically. But&amp;nbsp;is it necessary to have version control on SDK files? My suggestion would be only to track project-specific files. If&amp;nbsp;there are any SDK source files you need to change, you can&amp;nbsp;put those into your project directory before you start tracking them with Git. This approach should also make it easier to migrate your project to future SDK releases if that becomes relevant.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also, if you wish to move the project outside the SDK folder structure,&amp;nbsp;you can do that quite easily by opening the emProject file in a text editor and replace the relative paths with a custom variable as shown below.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-cbaa51d3888a4fa8bc8d5771efbf3229/Capture.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;The SDK_ROOT variable can be added and changed under &amp;#39;Solution&amp;#39; settings in SES (make sure it&amp;#39;s applied to the common configuration)&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/480x480/__key/communityserver-discussions-components-files/4/6811.Capture.PNG" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>