CCS/TIDA-01580: TIDA-01580 Software

Hi Sergey,

The link to your screenshot is broken. Can you repost?

If you continue to have issues with broken links, please see the below faq:

https://e2e.ti.com/support/tools/ccs/f/81/t/821597

Thanks

ki

My project 

'

Hi, ki

My  Tida-01580 project:

=========================================

.jxbrowser-data

.metadata

dvt

RemoteSystemsTempFiles

Support Files

tida-01580_firmware_tx

tida-01580_firmware_tx_stack_library

=========================================

Who is responsible for incoming projects in Workspace???

The greatest difficulty is the catalog   .metadata

.metadata/**.log
.metadata/**.ini

.metadata/**.markers

.metadata/**.pdom

.metadata/**.snap
.metadata/**.index
.metadata/**.xmi
.metadata/**.pdom
.metadata/**.txt
.metadata/**.resources
.metadata/**.lib     
.metadata/**.xml
.metadata/**.tree

.d  ???  

Maybe someone has a generated Ignore file?
I don't think I'm the only one interested in this issue.
I looked at the link but unfortunately there is clearly not enough information there.

Somewhere there should be descriptions of the extensions of the files used.

Sergey Andrienko said:

The greatest difficulty is the catalog   .metadata

I exclude the complete .metadata directory from being placed under configuration control, as it contains what consider per-user data such as history of edits and view settings. Not sure if ever found a good description of everything which gets stored in the .metadata directory.

If I exclude the directory .metadata , my projects do not open after clone all workspase.

Workspace EMPTY after clone ftom "server" !!!

Where is information about projects included in Workspace?

Sergey Andrienko said:

Workspace EMPTY after clone ftom "server" !!!

The .metadata directory holds the list of projects within the workspace.

After cloning from the server, and opening CCS as noted the workspace will be empty. You should be able to Project -> Import CCS Projects and then point at the workspace directory and be able to select the projects to import.

I tried this way. It is not comfortable. Shouldn't be handmade. Everything should happen automatically in one click. This is how we always work. If additional actions appear, they can introduce an inaccuracy or error. And this, unfortunately, is not the same.

This is not a version control system.

Thank you.

Chester Gillon said:

I exclude the complete .metadata directory from being placed under configuration control, as it contains what consider per-user data such as history of edits and view settings. Not sure if ever found a good description of everything which gets stored in the .metadata directory.

yes, it is a bit of a mystery. I always consider it storing all the custom information specific to that workspace.

https://stackoverflow.com/questions/19996170/what-is-the-metadata-folder-in-eclipse-workspace

In general, people usually do not need to check in the contents of .metadata into version control:

https://stackoverflow.com/questions/337304/which-eclipse-files-belong-under-version-control