• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 490 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.

CCS V5.4 Option File Parsing

Jordon
Intellectual 635 points

Hello,

I have found that in importing our 3.3 projects which uses a compiler option file that contain our conditional compile -D options, that the Eclipse editor does not pre-process the -D(s) in the option file so conditionally compiled code is grayed out and editor functions like find declaration, etc. will not work . Our team  would like to retain the use of the compiler option file vs. having those options declared in the project file. 

I would consider this a bug. Could someone at TI verify my scenario and let us know if you could address it in a future release? We are using CCS 5.4 but I have noticed this in earlier versions 5.3 etc. (as I recall). 

Regards, J

  • 0
    TI__Guru**** 162305 points

    Jordon,

    Historically the options files are just passed on directly to the compiler.  They are not scanned and interpreted by the build system.  i.e. include paths in there won't show up in the include folders and -D flags won't impact the conditional formatting...  I believe we did change the system to scan for include paths.  I can file a request to scan for -D / --define as well.

    The tracking number will be: SDSCM00048177


    Regards,

    John