• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 834 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.

CCSv6 Fixed build configuration for the indexer not applied

Julian S
Prodigy 200 points

Hello,


I'm experiencing an issue when trying to set a specific fixed build configuration for the indexer. I can choose it from the dropdown menu in Properties->C/C++ General->Indexer, but it is not actually applied after clicking "Apply". I can see the indexer runs after clicking, but it looks like its setting reverts to the currently active build configuration. When clicking "OK" and opening the properties again, the currently active build configuration is chosen instead of the one I selected. So it seems the setting is actually reverted.

In the workspace settings, at "Build configuration for the indexer" the option "Use the build configuration specified in the project's indexer settings" is checked.

Is there any other option I have to consider? I think I don't have to enable project specific settings for the indexer due to the workspace setting I mentioned. Nevertheless I tried doing so, but the behaviour is the same.


Any suggestions? Thanks in advance.

  • 0
    TI__Guru*** 130875 points

    Hi Julian,

    I am looking into this as I can easily reproduce this.  I will likely file a bug but will post further as I can.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Genius 9355 points

    Hi Julian,

    We have implemented this behaviour intentionally.  By default, CDT always uses the Debug configuration for indexing, regardless of the currently active configuration, which results in unexpected behaviour.  Allowing the user to manually select which configuration should be used for indexing also did not seem like a desirable feature to us.  So, CCS automatically adjusts this setting to always ensure that the currently active build-configuration is also the one that is used for indexing.

    Could you provide more details on your use-case?

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Prodigy 200 points

    Hi Baltasar,


    I am using TivaWare as a svn external to make it possible for others to checkout and compile the project without installing TivaWare before. Because of this I have to exclude its directory from build in my project. Otherwise the compiler also tries to compile everything in the TivaWare directory which results in errors.

    But this excluding from build seems to stop the indexer from looking into the TivaWare .c files. When I press F3 to a TivaWare method called in my code, I get to the .h file, but pressing F3 again then does not get me to the .c file. This only works if I created a new Project with TivaWare the usual way as described in http://processors.wiki.ti.com/index.php/Creating_new_CCS_v5_Project_with_Stellarisware (this is for Stellarisware but the procedure is almost identical with TivaWare).


    This made me try to let the indexer use an own build configuration where the TivaWare directory is not excluded from build.


    Maybe someone knows a better way to solve this?


    Thanks,

    Julian

  • 0 in reply to Julian S
    TI__Genius 9355 points

    Hi Julian,

    Could you try, instead of excluding the TivaWare directory from build, placing a hidden file named ".exclude" into that directory.  This is a less restrictive way to exclude a directory from build.

    Let me know if that solves your indexer problem.

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Prodigy 200 points

    Hi Baltasar,


    this works fine :)


    Thanks very much,

    - Julian