<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Saving a project in Source Control in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Saving-a-project-in-Source-Control/m-p/2163129#M52379</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252673"&gt;@ekmas-19&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;For both the &lt;STRONG&gt;save&lt;/STRONG&gt; and &lt;STRONG&gt;don't save&lt;/STRONG&gt; list, I agree.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For &lt;STRONG&gt;not sure&lt;/STRONG&gt;, I recommend keeping /.project, /.cproject and /.settings, in order to import/build the project without reconfiguring it manually (for compiler and CDT configurations).&lt;/P&gt;
&lt;P&gt;You can ignore /.metadata, as it normally includes workspace related configuration.&lt;/P&gt;
&lt;P&gt;Keep in mind that, for&amp;nbsp;reproducible&amp;nbsp;builds, the same RTD version (with patch) must be used.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;</description>
    <pubDate>Wed, 03 Sep 2025 21:09:44 GMT</pubDate>
    <dc:creator>Julián_AragónM</dc:creator>
    <dc:date>2025-09-03T21:09:44Z</dc:date>
    <item>
      <title>Saving a project in Source Control</title>
      <link>https://community.nxp.com/t5/S32K/Saving-a-project-in-Source-Control/m-p/2163012#M52377</link>
      <description>&lt;P&gt;I created a S32K344 Project. which files are need to be saved in source control?&amp;nbsp;&lt;/P&gt;&lt;P&gt;For sure the .mex file is required and the generated files would not be need as they can easily be recreated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My guess is as follows. Can someone confirm this?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Save&lt;/STRONG&gt;;&amp;nbsp; .mex and all files at this top level. /src, /includes, /Project Settings&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;don't save&lt;/STRONG&gt;; /RTD, /board, /generate, /Debug_Flash (or the equivalent in RAM or release), /RemoteSystemsTempFiles&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;not sure;&lt;/STRONG&gt;&amp;nbsp;/.settings, /.metadata, /.metadata/plugins&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Sep 2025 15:36:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Saving-a-project-in-Source-Control/m-p/2163012#M52377</guid>
      <dc:creator>ekmas-19</dc:creator>
      <dc:date>2025-09-03T15:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Saving a project in Source Control</title>
      <link>https://community.nxp.com/t5/S32K/Saving-a-project-in-Source-Control/m-p/2163129#M52379</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252673"&gt;@ekmas-19&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;For both the &lt;STRONG&gt;save&lt;/STRONG&gt; and &lt;STRONG&gt;don't save&lt;/STRONG&gt; list, I agree.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For &lt;STRONG&gt;not sure&lt;/STRONG&gt;, I recommend keeping /.project, /.cproject and /.settings, in order to import/build the project without reconfiguring it manually (for compiler and CDT configurations).&lt;/P&gt;
&lt;P&gt;You can ignore /.metadata, as it normally includes workspace related configuration.&lt;/P&gt;
&lt;P&gt;Keep in mind that, for&amp;nbsp;reproducible&amp;nbsp;builds, the same RTD version (with patch) must be used.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;</description>
      <pubDate>Wed, 03 Sep 2025 21:09:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Saving-a-project-in-Source-Control/m-p/2163129#M52379</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2025-09-03T21:09:44Z</dc:date>
    </item>
  </channel>
</rss>

