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.

CCS: I never want to execute non-compiling code but I always get asked

Tool/software: Code Composer Studio

If I Run from CCS Edit and the build fails (due to a syntax error or similar problem) I get an "Errors in Workspace" dialog that allows me to "Proceed" of "Cancel".

The dialog includes a checkbox "Always launch without asking". I'd much rather a checkbox that said "Never launch broken builds". I'd also rather be returned to CCS Edit mode rather than be left in CCS Debug mode.

Instead of the checkbox a list of Radio Buttons could be used:

  • Never launch broken builds
  • Always prompt for broken builds
  • Always launch even when a build is broken

This change would require the "Launch Options" for "Auto Run and Launch Options" on the "Target" tab of the "Edit launch configuration properties" dialog to be updated.

  • Hi,

    That request makes sense. I will investigate a few details and report back with my findings - we may have a workaround or perhaps an enhancement needs to be filed. 

    I apologize for the inconvenience,

    Rafael

  • Hi,

    I have filed the enhancement request CCSIDE-3616 and, in about half hour, you can check its status in the link SDOWP in my signature below. 

    In the case this is not doable due to other unknown (at least to me) details, I propposed an alternative to make the "Cancel" button to automatically return to the CCS Edit Perspective. 

    Regards,

    Rafael

  • Hi Rafael,

    I get "Record 'CCSIDE-3616' was not found" for that ticket.

    Cheers, Peter

  • Peter, 

    The system seems rather slow - it usually kicks in after about half hour. 

    I will see what is going on.

    Regards,

    Rafael

  • Peter,

    The system that pushed the rerpots was offline. Please retry now. I can see it on the SDOWP database.

    Regards,

    Rafael

  • Hi Rafael,

    thanks for that, I see it now.

    I'm somewhat puzzled about how option 2 ("Simply set the "Cancel" button to automatically return to CCS Edit perspective") would work. Would the "Errors in Workspace" dialog never show again after clicking "Cancel", or would it show as now every time there is a build error during launch, but fall back to edit rather than debug?

    My strong preference, although I appreciate it is more work, is for option 1 so in effect I never leave the edit perspective when a build fails. Anything else adds extra steps to getting the problem resolved and getting on with the task at hand.

    Cheers, Peter

  • Peter,

    Peter Jaquiery said:
    I'm somewhat puzzled about how option 2 ("Simply set the "Cancel" button to automatically return to CCS Edit perspective") would work. Would the "Errors in Workspace" dialog never show again after clicking "Cancel", or would it show as now every time there is a build error during launch, but fall back to edit rather than debug?

    That would be the expected behaviour.  

    As I mentioned before, this is a compromise given that I am unsure how the detection of a failed project/inexisting .out file happens under the hood of CCS - in other words, it may happen only when the CCS Debug Perspective is opened as part of the underlying Eclipse Debug launch process.

    At any rate, I will indicate to the dev team which option is the preferred one. 

    Regards,

    Rafael

  • OK, understood. Thanks Rafael.

    Cheers, Peter