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.

Forcing multiple configurations to build before debugging

The title for this post is a mess, so I'll rephrase it using an example:

I have a project that is targeting two processors on the same JTAG scan-chain. The two processors need to run nearly identical code, but there are a few minor differences. To keep things simple, I implemented this as a single CCS project with two build configurations. Let's call the configurations Config A and Config B. The two build configurations use a pre-defined symbol (defined in one configuration and not the other) to allow each configuration to build slightly different versions of the same project. I also set up the project's Debug Configuration to load the binary from each build configuration onto the correct processor, and again, everything works as expected.


I have one minor annoyance though. Typically, when you debug a project in CCS, the project will perform an incremental build before loading the binary. The problem is, with my setup, only the currently selected build configuration runs the automatic incremental build, even though the output from both build configurations is needed for the debug operation. As an example, if I make a change that affects both Config A and Config B (i.e. the change isn't inside an #ifdef on the pre-defined symbol) while Config A is selected as the active build configuration, if I debug without manually building both configurations, only Config A is automatically updated; the debugger happily loads the outdated binary from Config B even though its source has changed.

This isn't a big deal, since I just need to remind myself to build both configurations manually before debugging. I'm just wondering if there's any way to "link" the debug configuration and build configurations, such that the debugger is smart enough to know that it should incrementally build each configuration whose output it is loading. I'm 99.9% sure that this is impossible since it seems like the debugger has no concept of build configurations (aside from knowing the active one)  but I thought I'd toss this out there.