Saving a project in Source Control

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Saving a project in Source Control

Jump to solution
231 Views
ekmas-19
Contributor II

I created a S32K344 Project. which files are need to be saved in source control? 

For sure the .mex file is required and the generated files would not be need as they can easily be recreated. 

My guess is as follows. Can someone confirm this?

Save;  .mex and all files at this top level. /src, /includes, /Project Settings

don't save; /RTD, /board, /generate, /Debug_Flash (or the equivalent in RAM or release), /RemoteSystemsTempFiles

not sure; /.settings, /.metadata, /.metadata/plugins

 

Tags (2)
0 Kudos
Reply
1 Solution
207 Views
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @ekmas-19,

For both the save and don't save list, I agree. 

For not sure, I recommend keeping /.project, /.cproject and /.settings, in order to import/build the project without reconfiguring it manually (for compiler and CDT configurations).

You can ignore /.metadata, as it normally includes workspace related configuration.

Keep in mind that, for reproducible builds, the same RTD version (with patch) must be used. 

Best regards,
Julián

View solution in original post

0 Kudos
Reply
1 Reply
208 Views
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @ekmas-19,

For both the save and don't save list, I agree. 

For not sure, I recommend keeping /.project, /.cproject and /.settings, in order to import/build the project without reconfiguring it manually (for compiler and CDT configurations).

You can ignore /.metadata, as it normally includes workspace related configuration.

Keep in mind that, for reproducible builds, the same RTD version (with patch) must be used. 

Best regards,
Julián

0 Kudos
Reply