What are best practices using the MATLAB Embedded Coder with Version Control (git)?

3 次查看（过去 30 天）
sschumm
sschumm 2023-9-5
评论： Dennis Hirth 2024-2-12
I'm trying to setup a project to generate C code from a Simulink model. The generated code will be used by external existing code. Git is used for version control.
The Embedded Coder generates a lot of files additional to the "relevant" .c and .h files like:
  • buildInfo.mat
  • codedescriptor.dmr
  • codeInfo.mat
  • compileInfo.mat
  • defines.txt
  • modelsources.txt
  • rtw_proj.tmw
  • trwtypeschksum.mat
  • ...
Most of these files are binary and there seems to be no benefit in tracking them with git.
I already figured out that "View Code" in Simulink is not possible when cloning a repository without the buildInfo.mat. So this seems to be a file that should be tracked by git.
What's the benefit in tracking the other files?
Is there a "best practice" on which files should be included in version control?
Which files are necessary that someone else can continue working with the embedded coder after cloning my remote repository?
Thanks for any advice :)

请先登录，再回答此问题。

回答（0 个）

类别

在 Help Center 和 File Exchange 中查找有关 Deployment, Integration, and Supported Hardware 的更多信息

标签

产品


版本

R2020a

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by