CODECOMPOSER: default projects/workspaces path

Part Number: CODECOMPOSER

Tool/software:

After changing the default workspace my new projects are still saved in

.config/Texas Instruments/CCS/.ccs-server/workspaces/

how to change the default projects path?

Also I don't get the difference between project amd folder-
There are some guidelines somewhere?

thank you

  • Hello,

    .config/Texas Instruments/CCS/.ccs-server/workspaces/

    This location is the workspace metadata location. Projects really should not be physically imported to that location.

    What CCS exact version are you using and what type of projects are you importing? Are they custom projects?

    Note that CCS 20.1.0 is now available. This version has some additional workspace fixes so if you are not on that version you may want to try it out.

    Thanks

    ki

  • I'm using v20.1.0.6__1.7.0

    Actually my workspace file is in a location chosen by me along with other projects folders.
    if I do File->import project (I see no other way to add an existing projet to current workspace) the 'import project" windows gives no way to change the destination. The only choice is "copy imported project into: workspace_csstheia". Even if currently a workspace is yet open in css there's no choice to add imported project to current workspace path.

    Same goes for "create new project" where there's no choice for destination folder.

    In the latter case ("create project") there's also a bug: the same template cannot be imported twice because the "project name" change has no effect. If I import "hello" example twice on the sencond try the answer is "a project with the name hello" already exists" even if I've changed the "Project name" field.
    That's annoying also because there's no way to create an empty project so starting from "hello" template seems the most practical way.

  • he only choice is "copy imported project into: workspace_csstheia". Even if currently a workspace is yet open in css there's no choice to add imported project to current workspace path.

    If workspace_ccstheia is the workspace folder being used, then that would be adding the project to the current workspace path. You should also have the option to import the project it its original location.

    Same goes for "create new project" where there's no choice for destination folder.

    This is by design. This method will always import to the current workspace folder

    In the latter case ("create project") there's also a bug: the same template cannot be imported twice because the "project name" change has no effect.

    Yes, this is a known issue: https://sir.ext.ti.com/jira/browse/EXT_EP-12242

    I'm still trying to understand how projects are getting imported to the workspace metadata location. Can you share your *.theia-workspace file that you are using?

  • If workspace_ccstheia is the workspace folder being used, then that would be adding the project to the current workspace path. You should also have the option to import the project it its original location.

    No, workspace_csstheia is the only choice even if another workspace is currently opened. Also why there's a choice box if the chice is only one?

    This is by design. This method will always import to the current workspace folder

    Not on my system.

    I'm still trying to understand how projects are getting imported to the workspace metadata location. Can you share your *.theia-workspace file that you are using?

    I have none. I'm trying NOT use it, even if css still insists to create it in my home folder, which is not my choice for sources. So I have to remove project from workspce_theia (which i delete because there's no way to change its path), move the created project to my destination and add it to my current workspace, That's annoying.

  • No, workspace_csstheia is the only choice even if another workspace is currently opened.

    You typically have two choices unless the project itself explicitly adds this restriction.

    Note that importing projects from the New Project Wizard or directly from Resource Explorer will always default to copying to the current workspace folder and this cannot be changed.

    I feel like there is some corruption with your environment. Can you try clearing all the caches mentioned in the link below:

    https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_faqs.html#i-want-to-restart-code-composer-studio-with-a-fresh-environment-how-do-i-do-this

    and complete delete the workspace_ccstheia folder. Then restart CCS and try importing some example project from project wizard or resource explorer. It should go to the default workspace_ccstheia folder.

  • Goti it. Solution is not use workspaces (which are not the same as folders)

    If a workspace is open than the inported or created new project goei in the wrokspace file but not in the workspace folder: project folder is created in ~/workspace_thea anyway, even if the new project is addedd to the currently opened workspace file.

    Instead opening just a folder without any workspace file (which can contain multiple projects subfolder) the new added project is created inside the current folder, as expected.

    The workspace concept is somehow confusing, the good is tha is not required.