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.
Tool/software:
As a follow-up to the related question that newer saw an answer.
We solved it by copying the generated .launch file from the .launches folder, put it into out git repo, and added a <file action="copy"..../> to the projectspec that kopies the .launch file into a folder below the project folder.
Actually we copy it to the "${project-loc}/targetconfigs" folder...
Here I reach my new question, i can't find anywhere in the manual where CCS will search for .launch files?
Hello,
i can't find anywhere in the manual where CCS will search for .launch files?
Please see: https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#debug-configurations
Thanks
ki
Hi KI
I have read that doc, but i find only information on default naming of the default .lauch files. But nothing on the search path?
You are looking for the location of the launch files (and where CCS looks for them), correct?
I know that if CCS generates them, it will put them in the "<PROJ_ROOT>/.launches" folder, and name them <project_name>.launch
But I saw that when i placed a .launch file in "<PROJ_ROOT>/targetConfigs" folder CCS did find it and used it.
I also saw that in a typical system project setup, i.e. "sys_project" with reference to "cpu1_project" and cpu2_project, if I placed "sys_project.launch" in "sys_project/targetConfigs" and "cpu1_project/targetConfigs", I got two options both named sys_project in the dropdown menu on the "Debug" button.
Note: For the obvious question "Now why would he do that?" Well it was actually a side effect of the targetConfigs folder being a link to the same folder from both projects!
So my question is where do CCS search for the lunch files?
And is there a way to direct CCS as to where to search?
Regards Martin
So my question is where do CCS search for the lunch files?
Besides the default paths where they are generated, any *.launch file added/linked to an open project in the active workspace will be detected.