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.

CCS5.5 console build sleeps for several minutes

My team and I recently upgraded our development environment from CCS3.3 to CCS5.5.0.00077. We are using a Windows 7 virtual machine on a dedicated pc to perform daily builds of our projects. The build is done via build scripts in the following way:

  1. Copy a workspace template with already imported projects into working directory
  2. Build projects via
    eclipsec.exe [...] -application com.ti.ccstudio.apps.projectBuild [...]

While this works in general, I am having problems with the build speed. The build, which should take about 1.5 to 2 hours, needs over four hours to finish.

When observing the progress in the console, the first thing I noticed was that the build seems to be sleeping for serveral minutes between the message "Finished building target" and the beginning of the post-build step. In the task manager, I can see that gmake is working heavily (on one core). So my first questions is: What is gmake doing during that time and what can be done to speed that up? (It may have something to do with 'verifying contents of the .pp-files?)

And finally a more general question: Instead of using a workspace template, would it be better to create a new workspace and import the projects for every build?

  • Hello,

    Ruediger Casper said:
    The build, which should take about 1.5 to 2 hours

    How did you come to this determination? Are you comparing it to CCSv3?

    Ruediger Casper said:
    sleeping for serveral minutes between the message "Finished building target" and the beginning of the post-build step.

    What does your post build step do?

    Ruediger Casper said:
    And finally a more general question: Instead of using a workspace template, would it be better to create a new workspace and import the projects for every build?

    It should not matter. You should be able to use an existing workspace with projects already imported with no problem (or delays).

    Thanks

    ki

  • Hi,

    Ki-Soo Lee said:

    The build, which should take about 1.5 to 2 hours

    How did you come to this determination? Are you comparing it to CCSv3?

    [/quote]

    No, that is the time it takes when I build via Code Composer GUI on a developer pc (identical hardware). I already allowed for some additional time because of the virtual machine eating some performance, but that can not mean another two hours - especially since a visual studio build done later in the process does not have a significant delay compared to a non-vm-build.

    Ki-Soo Lee said:

    sleeping for serveral minutes between the message "Finished building target" and the beginning of the post-build step.

    What does your post build step do?

    [/quote]

    It copies the generated library to a different directory as "backup".

  • Solved: VMWare Workstation 9 was the problem - it works fine with version 10.