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 insists on doing clean build for some configurations

Other Parts Discussed in Thread: CCSTUDIO

Hi

I am doing a headless build using CCS5.5.  For one of my project configurations 'Debug' CCS insists on doing a FULL build even though I have specified INCREMENTAL:

C:\ti\ccsv5\eclipse>eclipsec -noSplash -data c:/jenkins/workspace/Osiris_trunk/workspace_jenkins_Osiris_trunk -application com.ti.ccstudio.apps.projectBuild -ccs.projects Osiris2_K2KCoreA -ccs.configuration Debug -ccs.buildType incremental

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Tue Feb 11 15:12:37 GMT 2014]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...


================================================================================
Building...


**** Clean-only build of configuration Debug for project Osiris2_K2KCoreA ****

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k clean
DEL /F  "configPkg\linker.cmd" "configPkg\compiler.opt"  "Osiris2_K2KCoreA.out"


For another configuration, CCS correctly does an incremental build.

How can I fix this please?

David

  • Hi David,

    What happens when you remove the explicit incremental option? Does it always do a clean rebuild? The default behavior should be incremental.

  • Yes, I noticed that the default behavior should be incremental. But, if I omit the incremental option it still does a clean build.

    Strangely, if I build another configuration it correctly does an incremental build.  But, for that same configuration, if I specify the build type as full, it still does an incremental build.

    There is something strange going on here.

    David

  • David Aldrich92784 said:
    There is something strange going on here.


    Looks like it. We've seen these types of issues pop up from time to time. Never knew exactly why they happen. We've made fixes in the past to make it more robust but looks like we're not all there yet.

    Can you try using a new workspace and importing your projects to it?

  • Hi Ki

    Thanks - I will try your suggestion of a new workspace.

    I think I have found another issue with the command line.  If I try to import a project into a workspace that already has that project, the command fails (as expected) but it does not set ERRORLEVEL to 1:

    C:\ti\ccsv5\eclipse>eclipsec -noSplash -data c:\<snip> -application co m.ti.ccstudio.apps.projectImport -ccs.location "C:\<snip>"

    --------------------------------------------------------------------------------

    Importing project from '<snip>'...

      !ERROR: A project with name 'K2KCoreA' already exists in the workspace!

    C:\ti\ccsv5\eclipse>echo %ERRORLEVEL%

    0

    Best regards

    David

  • Hi Ki

    Please will you raise a bug report for the following issue?  We can then close this thread.

    David Aldrich92784 said:

    I think I have found another issue with the command line.  If I try to import a project into a workspace that already has that project, the command fails (as expected) but it does not set ERRORLEVEL to 1:

    C:\ti\ccsv5\eclipse>eclipsec -noSplash -data c:\<snip> -application co m.ti.ccstudio.apps.projectImport -ccs.location "C:\<snip>"

    --------------------------------------------------------------------------------

    Importing project from '<snip>'...

      !ERROR: A project with name 'K2KCoreA' already exists in the workspace!

    C:\ti\ccsv5\eclipse>echo %ERRORLEVEL%

    0

     

    Best regards

    David

  • Done. Tracking ID is: SDSCM00049534

    I filed it against CCSv6 since I can reproduce it there also (and since v5 is nearing the end of the road in regards to support/updates)

    Note that the issue appears Eclipse related (meaning it is something we inherited from Eclipse instead of the CCS team owning it). This type of issues take us longer to resolve because we don't have control over it and need to request fixes to the Eclipse community.

    thanks

    ki