• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 6304 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

"Build all" gives CDT error now in Version: 5.2.1.00018

Greg Buchholz
Prodigy 30 points
Other Parts Discussed in Thread: SYSBIOS

    I just did the update option to get my installation of CCS to 5.2.1.00018.  Everything thing appears to work fine, until a hit the "Project -> Build All" button.  Then I get the following error message:

Errors occurred during the build.
Errors running builder 'CDT Builder' on project 'ccm_sysbios'.
Generated resource conflict:
two resources of the same name: /ccm_sysbios/Debug/.metadata/.plugins/org.eclipse.cdt.make.core/specs.obj
generated by different tools
tool1: C2000 Compiler
tool2: C2000 Compiler
 
Generated resource conflict:
two resources of the same name: /ccm_sysbios/Debug/.metadata/.plugins/org.eclipse.cdt.make.core/specs.obj
generated by different tools
tool1: C2000 Compiler
tool2: C2000 Compiler
 
Generated resource conflict:
two resources of the same name: /ccm_sysbios/Debug/.metadata/.plugins/org.eclipse.cdt.make.core/specs.obj
generated by different tools
tool1: C2000 Compiler
tool2: C2000 Compiler
 
Generated resource conflict:
two resources of the same name: /ccm_sysbios/Debug/.metadata/.plugins/org.eclipse.cdt.make.core/specs.obj
generated by different tools
tool1: C2000 Compiler
tool2: C2000 Compiler
 

...I can build successfully if I do a "Project -> Clean...", or wipe my "Debug" build directory.  But then it comes back again when trying the "Build All".  Everything was working correctly under CCS 5.1.1.  I find it interesting that it appears to be complaing about a specs.obj file that doesn't exist.  The issue might also be related to the one described here:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/203656/726567.aspx

...the "fixes" described in that thread don't seem to work, especially since I don't have a .gconf directory anywhere.  Also of interest is that those files have nothing to do with what I want to build, and the specs.c and specs.cpp that are in my workspace are empty (1-byte) files.  I have a work-around, in the form of building clean each time, but I wonder if anyone else is having a similar problem, or know the proper fix.

Thanks,

Greg

  • 0
    Prodigy 30 points

    I seem to have cured the issue be deleting all the .metadata directories lying around, including in the Debug and Release directories, and their parents.

  • 0 in reply to Greg Buchholz
    TI__Guru*** 130875 points

    Hi Greg,

    thanks for the update and glad you found a work around.  Check out this related post as a bug was filed against this.  The issues seems to be with the hidden folders/files.

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/203656/737690.aspx#737690

    Best regards and all the best with development,

    Lisa