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/CC1352R: Using a build variable to create a pre-defined symbol doesn't work the way it used to - Compilation works fine, Editor features don't.

Part Number: CC1352R

Tool/software: Code Composer Studio

It used to be that you could create a pre-defined symbol like so:

Then, when you build, you get a --define=QX_008_752_T_HANDLE, which can be used to ifdef things in and out. This still works fine. What doesn't work is the IDE showing which code blocks are compiled in vs out. That feature doesn't work when you do this.

If you then add "QX_008_752_T_HANDLE" to the list of pre-defined symbols directly, it works for the build, and the editor features then work. Having this work is great when managing a larger number of similar builds.

This used to work correctly in CCS 8.2, stopped working in 8.3, and continues to not work in CCS 9.0

  • Joshua van Tol said:
    It used to be that you could create a pre-defined symbol like so:

    The attachment did not come through. Could you please attach it again so we understand how you are creating the symbol? Thanks.

  • Okay, somehow I was able to see the screenshot in the preview, but it didn't stay.

    I added the following to the pre-defined symbols

    ${ConfigName}

    ${ConfigName} resolves to QX_008_752_T_HANDLE

    So, if you just define ${ConfigName} the build works correctly, and all the conditionally compiled stuff in the code that relies on QX_008_752_T_HANDLE being defined is correctly compiled. But when you view it in the editor, CCS thinks that define isn't active and greys out the code. Anything inside those blocks also doesn't appear in C/C++ search results.

    Directly adding QX_008_752_T_HANDLE to the pre-defined symbols works fine, but is less convenient for my use case.
  • Thanks for the details. I can reproduce this. I will check to see if there is anything already filed to track this, if not, I will file a bug report and then post an update here.
  • Great! Having this be broken isn't killing me, but it was nice while it worked and made my workflow more productive.
  • Sorry about the delay. The tracking ID for this issue is CCSIDE-3542. Feel free to track it using the SDOWP link in my signature.