CCS: More 'help description' would be useful to clearly explain what are the best practices for workspace and project cloning, copying and moving

Hi Vlad,

Any documentation / best practices that exist for Eclipse workspaces would apply also for CCS workspaces. There are many out there. For example:

https://dzone.com/articles/eclipse-workspace-tips

https://mcuoneclipse.com/2013/02/02/eclipse-workspace-tips/

https://stackoverflow.com/questions/2493997/eclipse-and-copying-workspaces

https://developers.redhat.com/blog/2013/09/24/separating-ide-wkspcs-code-repos/

In general, it is not recommend to copy workspaces folders around as workspaces are not designed to be portable. But it is possible as some of the links discuss. The .metadata may contain some paths that could become invalid if the workspace is copied to a location different from its current directory. 

There are no issues with multiple users sharing the same workspace folder on a machine - as long as the workspace folder is read/write accessible to all users (for example, having the workspace folder in one users home folder could create issues for obvious permissions reasons). There is one small caveat when sharing workspace folders this way - the default folder for target configuration files is inside the user's home folder. So if you create a global target configuration file, which appears in the 'User Defined' node of the Target Configurations view, and then have a different user log in and use the same workspace, that user will not see that target config file since CCS will be using that user's home directory for the default target configuration folder. This is the case even though the workspace folder being used is the same. Note that the default target configuration folder user by a workspace can be configured to a common fixed location to avoid this.

Copying workspaces to other machines for use is not something recommended or supported by Eclipse

As for projects, many details are covered in the Project and Build Handbook, including sharing projects and making them portable.

http://dev.ti.com/tirex/#/?link=Development%20Tools%2FIntegrated%20Development%20Environments%2FCode%20Composer%20Studio%2FProjects%20and%20Build%2FDocuments%2FUser's%20Guides%2FProject%20and%20Build%20Handbook

Of course we are always looking to improve our documentation and your feedback highlights that we still have a ways to go. We will certainly keep your feedback in mind as we update our documentation.

Thanks

ki