Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1246 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/CCSTUDIO: Edit Build-Flags dialog is buggy

Tim Redfern
Expert 1360 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

I've been seeing stupid issues with this single I started using CCS and they don't seem to be going away

1. When I type '--' (double hyphen) to begin defining a compiler flag, the editor changes it to '—' (a continuous decorator line) after a split second. This is so annoying! I have to cut and paste hyphens to define new flags

2. Something is broken in the algorithm for escaping quotations. The dialog starts adding \ before every " and the contents of include path strings become inoperative. Thus --include_path="${CG_TOOL_ROOT}/include" becomes include_path=\"${CG_TOOL_ROOT}/include\" and doesn't work. When I correct it, and hit 'OK', the errors are re-introduced. It's as if the algorithm for determining what's inside quotations (thus needing escaping) is broken. This is unbelievably annoying! 

I'm using CCS 7.4 on OSX

  • 0
    Expert 1360 points
    Also there's another bug, where when I make an edit, a new copy of the entire build flags is pasted in after the original, in quotations
  • 0 in reply to Tim Redfern
    TI__Guru**** 161100 points

    Tim,

    I see the same thing with the -- becoming - in the Edit Flags dialog.  I am also on a Mac.   Personally I only use the manual Edit Flags if the option is not available via the normal options settings.

    For example the include paths I manage here:

    I see something different but equally odd with quotes.  I added an include path for the compiler root location macro but it seems to put extra quotes around it and in what it shows the macro is gone.  The sets of quotes are also different.

    I will need to follow up with someone on this.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Guru**** 161100 points
    I have filed CCSIDE-3283 and CCSIDE-3284 to track these. For now I would recommend using the options in the dialog instead of using Edit Flags to manually change them.

    Regards,
    John
  • 0 in reply to JohnS
    TI__Expert 8765 points

    FYI, this "smart" behaviour is specific to Mac OS, and is enabled by default.  Starting with v4.8, Eclipse added code to disable this behaviour in the context of the running Eclipse app (CCS is currently on Eclipse v4.7) - 

    Until CCS picks up Eclipse v4.8, the user can disable the smart substitution behaviour system-wide:

    1. Open System Preferences.
    2. Go to Keyboard, then open the Text tab.
    3. Uncheck the "Use smart quotes and dashes" checkbox.

    Thanks,

    - Baltasar