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: CCS Include Paths Disappear after Adding

Tool/software: Code Composer Studio

Hello,

We built a collection of libraries that are included across many different projects.  We have an encountered an issue that is hard to reproduce but wanted to bring your attention to it and see if this is a known bug.  

We have seen this issue since CCS 7 but are now using CCS 9.0.1.0004 on Windows 10 systems.  We have libraries that have 16 include paths.  If we add an additional include path and hit "apply and close" sometimes the include path will not persistent when we examine it again.  To ensure the include path sticks we always have to verify that the include path list. 

I didn't see any commentary on the forums but wanted to check if this is something that has been seen? 

-Jason  

  • Jason,

    I haven't heard of this issue before. 

    Jason Haedt said:
    If we add an additional include path and hit "apply and close" sometimes the include path will not persistent when we examine it again. 

    So is the path actually missing from the build - (e) when you look at the build console, does it show that the last path is not picked up? I'm just wondering if it is just a GUI display thing or if the build system is not picking up the path altogether. 

    An alternative option, if you have several include path options that is common among multiple projects, is to add them to an options file. An options file is simply a text file with a list of compiler options. Then pass the options file to the compiler --cmd_file option found under Project Properties->Build->Compiler->Advanced Options->Command Files. 

  • When this happens the path is also missing from the build.  It does not get picked up when we hit apply and close.  I will suggest the alternative option.  I appreciate your feedback on this.  

  • Jason Haedt said:
    When this happens the path is also missing from the build.  It does not get picked up when we hit apply and close.

    For one use-case where the include path is ignored, could you capture the full output of the CCS build console to a text file (as described in this page) and attach it here? Would be interesting to see if it gives any clues.

  • Jason,

    Since I haven't heard back on this I am going to close out this thread. However, it will still be interesting to see a use-case where the include path is ignored, if you have a chance to capture one and send to us.