<?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 MCUXpresso - What To Commit To Repository? in MCUXpresso General</title>
    <link>https://community.nxp.com/t5/MCUXpresso-General/MCUXpresso-What-To-Commit-To-Repository/m-p/1581892#M4829</link>
    <description>&lt;P&gt;I am using MCXpresso, and of course need to make sure that all of my work ends up in a source code repository.&lt;/P&gt;&lt;P&gt;I am pretty confident that I am capturing all the outputs of the process (such as auto-generated code) as they appear in my workspace,&lt;/P&gt;&lt;P&gt;What I need to confirm is all the INPUTS to the process that produced the output.&lt;BR /&gt;The .mex file seems to end up in the workspace, but are there any files outside the workspace that I really need to make sure are committed to the repository?&lt;/P&gt;&lt;P&gt;I just want to make sure if my laptop dies, a new person takes over the project, etc... that any user can drive the MCUXpresso creation process.&amp;nbsp; It seems reasonable that they need to install the version of MCUXpresso and the SDK that I originally used (which they should be able to get from NXP).&amp;nbsp; Then I just want them to have to clone the repository and open the workspace. So, are there any files outside the workspace that I need to explicitly capture?&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 12 Jan 2023 17:46:32 GMT</pubDate>
    <dc:creator>JK_265</dc:creator>
    <dc:date>2023-01-12T17:46:32Z</dc:date>
    <item>
      <title>MCUXpresso - What To Commit To Repository?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/MCUXpresso-What-To-Commit-To-Repository/m-p/1581892#M4829</link>
      <description>&lt;P&gt;I am using MCXpresso, and of course need to make sure that all of my work ends up in a source code repository.&lt;/P&gt;&lt;P&gt;I am pretty confident that I am capturing all the outputs of the process (such as auto-generated code) as they appear in my workspace,&lt;/P&gt;&lt;P&gt;What I need to confirm is all the INPUTS to the process that produced the output.&lt;BR /&gt;The .mex file seems to end up in the workspace, but are there any files outside the workspace that I really need to make sure are committed to the repository?&lt;/P&gt;&lt;P&gt;I just want to make sure if my laptop dies, a new person takes over the project, etc... that any user can drive the MCUXpresso creation process.&amp;nbsp; It seems reasonable that they need to install the version of MCUXpresso and the SDK that I originally used (which they should be able to get from NXP).&amp;nbsp; Then I just want them to have to clone the repository and open the workspace. So, are there any files outside the workspace that I need to explicitly capture?&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jan 2023 17:46:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/MCUXpresso-What-To-Commit-To-Repository/m-p/1581892#M4829</guid>
      <dc:creator>JK_265</dc:creator>
      <dc:date>2023-01-12T17:46:32Z</dc:date>
    </item>
    <item>
      <title>Re: MCUXpresso - What To Commit To Repository?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/MCUXpresso-What-To-Commit-To-Repository/m-p/1581902#M4830</link>
      <description>&lt;P&gt;Basically you should ignore the build output folders (Debug, Release).&lt;/P&gt;&lt;P&gt;There has been a debate (see for example &lt;A href="https://mcuoneclipse.com/2018/09/30/tutorial-git-with-eclipse/" target="_blank"&gt;https://mcuoneclipse.com/2018/09/30/tutorial-git-with-eclipse/&lt;/A&gt; ) about ignoring the .settings folder too (which I do, but this depends on what extra folders you are using).&lt;/P&gt;&lt;P&gt;So my 'standard' ignore file is like this one:&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/ErichStyger/mcuoneclipse/blob/master/Examples/MCUXpresso/FRDM-K22F/FRDM-K22F_littleFS/.gitignore" target="_blank"&gt;https://github.com/ErichStyger/mcuoneclipse/blob/master/Examples/MCUXpresso/FRDM-K22F/FRDM-K22F_littleFS/.gitignore&lt;/A&gt;&lt;/P&gt;&lt;P&gt;(note: I don't have a 'Release' configuration, but that's another story)&lt;/P&gt;&lt;P&gt;In the above case I'm not using the config too .mex file, otherwise I would Ignore it too, because all the information is stored in the source files, so the .mex is redundant.&lt;/P&gt;&lt;P&gt;There is another special case, if you decide to turn off the auto-generated linker file in the linker project settings. In that case you should not ignore the *.ld files, see for example&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/ErichStyger/mcuoneclipse/blob/master/Examples/MCUXpresso/LPC55S16-EVK/LPC55S16_PositionIndependentCode/.gitignore" target="_blank"&gt;https://github.com/ErichStyger/mcuoneclipse/blob/master/Examples/MCUXpresso/LPC55S16-EVK/LPC55S16_PositionIndependentCode/.gitignore&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jan 2023 18:28:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/MCUXpresso-What-To-Commit-To-Repository/m-p/1581902#M4830</guid>
      <dc:creator>ErichStyger</dc:creator>
      <dc:date>2023-01-12T18:28:03Z</dc:date>
    </item>
  </channel>
</rss>

