• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 2313 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/CODECOMPOSER: Disable indexing for headless builds

Simon Falsig
Intellectual 350 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CC2650, CCSTUDIO

Tool/software: Code Composer Studio

I'm currently integrating a build of a CC2650 project into our Jenkins CI system, and for that I'm using the headless functionality of CCSv7. This works relatively well (considering it's headless Eclipse), except that it uses quite a bit of time indexing the projects after import. Since the process is purely headless, going straight from import to building, the indexing is completely unnecessary in this case, so I'd like to know if there's any way of turning it off?

I've tried the "-no-indexer" commandline option when calling eclipsec, but I still see output (enabled with -consoleLog) that indexing is happening:

!ENTRY org.eclipse.cdt.core 1 0 2018-05-08 16:57:31.430
!MESSAGE Indexed '<project-name>' (48 sources, 421 headers) in 43.3 sec: 31,370 declarations; 66,655 references; 182 unresolved inclusions; 76 syntax errors; 1,119 unresolved names (1.1%)

My process is the following:

eclipsec -noSplash -no-indexer -consoleLog -data <workspace> -application com.ti.ccstudio.apps.projectCreate -ccs.projectSpec <projectspec-file>

eclipsec -noSplash -no-indexer -consoleLog -data <workspace> -application com.ti.ccstudio.apps.projectBuild -ccs.configuration Debug -ccs.buildType "incremental" -ccs.projects <project-name>

The indexing seems to happen during the projectBuild step.

Is there any way of turning off indexing that works? Preferably without touching the projectspec files, as I still want indexing to be enabled for development, where I don't use headless builds...



  • 0
    TI__Guru**** 173310 points

    Simon Falsig said:
    I've tried the "-no-indexer" commandline option when calling eclipsec, but I still see output (enabled with -consoleLog) that indexing is happening:



    I see the same behavior - the indexer runs even when the -no-indexer option is specified, so the option does not seem to get set on the project. However, I see that the indexer runs the first time the project is imported and built in a new workspace, but successive builds do not trigger that "Indexed" message. Is that what you see as well?

    Not the most ideal solution, but one workaround could be to use the CCS GUI to turn off the indexer for a particular workspace, then do the headless import and build in that workspace.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Simon,

    Hopefully the workaround suggested helps you move forward on this. We will go ahead and close this thread for now but please feel free to post a reply or start a new thread if there are other questions.
  • 0 in reply to AartiG
    Intellectual 350 points

    Thanks for the answer! You are right though - it only happens after a new import.

    However, since I haven't been able to find a way of actually removing projects from a workspace, the only way to do a clean build if the projectspec file changes, is to completely remove the workspace and reimport into a new workspace - thus the workaround doesn't really work...

    Do you know of a way of removing projects, or at least reimporting a projectspec file into an existing workspace? I tried ccs.projectCreate with the -ccs.overwrite option, but that didn't seem to work either...

  • 0 in reply to Simon Falsig
    TI__Guru**** 173310 points

    Simon Falsig said:
    I tried ccs.projectCreate with the -ccs.overwrite option, but that didn't seem to work either...

    Did you try -ccs.overwrite full? That worked for me to reimport a modified projectspec into the existing workspace. 

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Simon,

    Were you able to try out the -ccs.overwrite full option to see if that helps?