• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 411 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CCS: Defect in Code Composer - Workspace and Custom project files not maintained properly for MotorWare projects

CCS: Code Composer, Motorware vs GIT continued

David Larson
Intellectual 310 points

Other Parts Discussed in Thread: MOTORWARE

Tool/software: Code Composer Studio

Just to clarify:  The problem is not where we decide to put our workspaces as that is a personal preference.  The problem with the design of how this works is where code composer puts modified files including the motorware lab project configuration files after you start a lab.   It is not completely putting project configuration files that end up being modified in the workspace.   If you install  Code Composer and Motorware from scratch, you have to manually make the same changes to the lab projects again. Sure, you can create a brand new project in your designated folder that you use GIT to maintain and copy all the source files there.  But if you want to keep track of changes you made to labs with GIT, it is not feasible to put the entire ti folder with motorware installed under GIT control.  It is also not worth the effort to try to extract all the necessary files from motorware and put them in a place more easily maintained by GIT as it confuses Code  Composer.  In my opinion, the files under motorware or c2000 should be considered read only and any files written to should be stored where they can be managed with source control like GIT.  Motorware and c2000 folders should only change with ti updates.

  • 0
    TI__Guru**** 475451 points

    Hi David,

    You are not the only one who has voiced this issue (or something similar). The issue is the structure of the Motorware package and the example projects. The lab projects pretty much uses only links to the original source file. CCS will only make a copy of source files inside the project folder (non-linked files) when the project is imported into a workspace. Hence this is a problem if you want to (or need to) make changes to those linked source files, yet preserve the original copy. Like yourself, people do not want to check in their whole source tree into version control. People have asked that CCS maintain a copy of the original source so that that the original content is not lost - similar to your suggestion. But that is not supported for linked files. Ideally, the projects in questions should not use linked files for files that is intended to be modified. Instead, they should be fully added to the project so that copy is made during the import of the project. I see this with examples from some other software packages - links for source files not intended to be modified, and non-links (file is actually added to the project) for files intended to be modified. Though not perfect, this works reasonably well and you would only need to check in source files inside the project folder

    I know this is not the answer you are looking for but I hope it explains the situation.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 310 points

    I realize the link to source is the way it is designed.  The thing that really bothers me is the project configuration files are in the Motorware folder tree, not in your workspace.  This means any configuration changes such as adding your own custom source files are lost if you re-install motorware.

  • 0 in reply to David Larson
    TI__Guru**** 475451 points

    David Larson said:
    This means any configuration changes such as adding your own custom source files are lost if you re-install motorware.

    Agreed. Any files that needs custom changes should be copied into the project folder in the workspace, instead of link to the original file in the motorware directory.