- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
I need to start new project B that is seeded with code from existing project A. The user manual states it can be done with simple copy/paste but does not work for me. I copy and paste, there is no error message, and no new copy of project A.
Manual also states that projects can be renamed by right clicking. I tried manually copying folder using windows and adding folder to workspace. That works but of course from CCS perspective project name is a duplicate so it is not treated as a project. I had thought that "rename" would solve that but right click on folder and there is no "rename" option.
no rename option here.
Can you either correct the CCS code or the documentation so they track? And how do I clone project A as starting code for new project B? Without manually copying and pasting the folder and then bulk editing the mystery config files using the dangerous
"sed -i s/project_A/project_B/g *.*"
and crossing fingers?
So I have now been at this for a good hour+ and nothing I do makes a "added folder" become a "project". Edited every file using grep and sed to change S100 to S200, added a s200 section to omnisense.theia-workspace, baically every pace I could think of I cloned or added. Please tell me you are not using the windows registry to add projects?!!
Hi Chris,
Please see my default project files architecture below. And a copy and paste based on the project under "Folder: xxx" workspace is normal. And it also works if we rename the paste project name.
Best Regards,
Pengfei
Are we using different tools? You seem to have 9 projects inside "Folder". I do not see how to do that. For me a "Folder" === "Project". I have multiple folders/projects under one workspace. If you right click on your "project" do you get build configurations menu item? I don't think so? How do you create a new project with multiple build configurations inside a "folder"?
This is tool I am using. What are you using?
Hi Chris,
I could not see the picture you attached. Do you miss something?
From the blow picture, you are placing your project files (source files, header files, debug folder and so on) under a "Folder:". But in our default project architecture, one or more "Projects" should be under the "Folder:", and for each project, they have their own source, header and debug files.
What I descript is the default file architecture, if I just import a project from our SDK:
Best Regards,
Pengfei
We do not seem to be communicating very well so let me try again. Below is what I am able/allowed to do by CCS. Circled in GREEN is my "Workspace". Within my "workspace" circled in YELLOW are my 3 "PROJECTS" (which you like to call "Folder"). Within a "PROJECT" circled in RED I have 4 build configurations. Thats what I have.
what YOU show is a TEST "Workspace" with 1 "Folder" (which is NOT A PROJECT!) that holds "9 projects". I DO NOT HAVE "xx projects" on the same line as my "Folders". And your documentation does NOT ALLOW FOR THAT TO HAPPEN. YOU ARE DOING SPMETHONG THAT IS UNDOCUMENTED. how are you doing it?
According to TI CCS documentation "The terms "folder" and "workspace" are sometimes used interchangeably. However, a workspace is a parent folder of a project (or projects) ". My "workspace" follows this rule. Your "workspace" does NOT. WHY and HOW are you violating this rule? Your "Workspace" "TEST" holds a "Folder" named "workspace_ccstheia" which holds 9 "Projects". You seem to have a workspace holding a folder/workspace holding 9 projects. I do not see a way to do that and the TI documentation does not allow it. How did you create a workspace inside a workspace???!!!! and why do I not see the word "Project" anywhere in my version of CCS? Look at my screenshot? Where is the word "project"? What version of CCS are you using?
Let me show you my workspace in this way:
It is NOT IMPARTANT whether the "Folder: workspace_ccstheia" has a upper layer folder, the point is, you need to place you project or projects under the "Folder", that is to say, you need to add another layer between your "Folder:S200" and your project configurations.
As you mentions the guidance document, "The terms "folder" and "workspace" are sometimes used interchangeably. However, a workspace is a parent folder of a project (or projects) ", here the "folder" and "workspace" represents the item with "Folder:" such as "Folder:S200" from your side and "Folder: workspace_ccstheia" from my side. And PLEASE ATTENTION THE "projects" in this sentence, you could place a project in this folder, and you could also place lots of "projects" in the folder. But even you just use a project, you need also create a project folder to includes you project configurations and this project folder is just under the "Folder:" workspace.
I was able to "Remove Folder from workspace" for my 3 "folder/project" projects and then re-add a new "folder" that was the windows parent directory "SW" of my three projects and all 3 projects were automatically "discovered" and now have a view that looks like yours. I consider this a bug that it was possible to have a "folder" == "project" and not even show/acknowledge it as a "project" yet seem to treat it as a project in all other ways. I can't tell you how I was able to create what should be a illegal project hierarchy. Seems like "Workspace"->"Folder(s)"->"project(s)" should be the only legal hierarchy yet I was able to create "Workspace"->"Folder/Project" and further everything worked but CCS never thought I actually had a "project". You need to clean this up.
