• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 634 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.

Project Level Predefined Symbols For Multiple Build Configurations

Kier
Mastermind 9110 points

Hello,

I have two build configurations. 90% of the predefined symbols are the same in both.

To avoid having to remember to insert a new predefined symbol into two build configurations, I'd like to define it once for the whole project.

Is there some way to define predefined symbols at the project level such that they are applicable for all build configurations please?

Thank you.


  • +1
    TI__Guru**** 464471 points

    For scenarios like this, I like to use an options file (--cmd_file, -@) that gets passed to the compiler. Multiple build configurations or projects would reference this file. Modifying all the compiler flags in this file would impact all the build configurations and projects that reference it.

    Thankd

    ki

  • 0 in reply to Ki
    Mastermind 9110 points

    Interesting. Thank you for that. Will look into it.

  • 0 in reply to Ki
    Mastermind 9110 points

    Just realised that this method bypasses the indexer and editor context (#ifdef/#else) formatting. I don't really want to lose this so I'll have to think of a another solution.

  • 0 in reply to Kier
    TI__Guru**** 464471 points
    Kier said:
    Just realised that this method bypasses the indexer and editor context (#ifdef/#else) formatting. I don't really want to lose this so I'll have to think of a another solution.

    This is true. We are looking to support this in CCS Theia however (having the indexer recognize predefined symbols in an options file).