• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 299 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CODECOMPOSER: Workspace with multiple folders, multiple projects, multiple launch.json files

Derrick
Intellectual 395 points

Part Number: CODECOMPOSER

Tool/software:

Our top-level project layout involves multiple folders, each of which has it's own subfolders that are standalone CCS projects. When we attempt to create a single workspace (file) and add each folder, CCS is able to identify the individual projects and build them. But, when we start creating Debug Configurations, the behavior seems random. Each project can contain it's own local launch.json file to hold Debug Configurations, but we could not figure out a way to direct CCS which file to use when configuring via the project's Properties > Debug tab (which then populates the launch.json file). It seems almost random which file it decides to use.

For example, the hierarchy could be:

Workspace
|- Folder 1
   |- Project A
   |- Project B
|- Folder 2
   |- Project C
   |- Project D

If I select project A and go to the project's Properties > Debug tab, it will sometimes populate the configuration in the launch.json file in Project B, C, or D instead. The name of that configuration is now even more confusing because in the Debug view, it's now called something like "Project A (Project B)".

How are we supposed to properly create Debug Configurations with the name and target launch.json file we intend?

  • 0
    Intellectual 395 points

    Is there a solution for this? This is just one of many commonly used features (opening additional windows, moving/resizing views used for debugging, macro expansion,  etc.) that worked on the old Eclipse-based CCS but don't work as well or are are simply not available on the new CCS. So far, this transition has been an overall downgrade for our team.