• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 693 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 4.2 with CGT 6.0.8

Matthew Waddell
Intellectual 255 points

 

I'm running into some trouble with getting CCS 4.2 to compile my application with CGT 6.0.8.  By way of background information: There are about 20 projects (19 produce libraries), and one project that links everything into a main application.  Each project has several build configurations (one per target: half a dozen).

 

The procedure I followed:

1)     Configured CCS4.2 to find the 6.0.8 toolchain (which is installed in the old ccs3.3 directory)

2)     For each project, I added an additional build configuration which uses the old 6.0.8 toolchain.

3)     Thought positive thoughts


Everything seems to compile just fine, but when it gets to the point of linking the main application together, the build fails, saying only: 

>> Compilation failure


There’s a log file in the workspace that shows a java exception):

!ENTRY org.eclipse.core.resources 4 566 2011-06-01 10:59:49.522

!MESSAGE An error occurred while traversing resources.

!STACK 0

java.lang.ArrayIndexOutOfBoundsException: 0

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription.composeOutputs(BuildDescription.java:542)

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription.access$1(BuildDescription.java:496)

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription$RcVisitor.doVisitFile(BuildDescription.java:206)

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription$RcVisitor.visit(BuildDescription.java:136)

            at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:57)

            at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:81)

            at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:85)

            at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:85)

            at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:126)

            at org.eclipse.core.internal.resources.Resource.accept(Resource.java:67)

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription.initDescription(BuildDescription.java:681)

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription.init(BuildDescription.java:704)

            at org.eclipse.cdt.managedbuilder.internal.buildmodel.DefaultBuildDescriptionFactory.createBuildDescription(DefaultBuildDescriptionFactory.java:37)

            at org.eclipse.cdt.managedbuilder.buildmodel.BuildDescriptionManager.createBuildDescription(BuildDescriptionManager.java:82)

            at org.eclipse.cdt.managedbuilder.internal.core.GeneratedMakefileBuilder.build(GeneratedMakefileBuilder.java:537)

            at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:603)

            at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)

            at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:167)

            at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

            at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:230)

            at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)

            at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:233)

            at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:307)

            at org.eclipse.core.internal.resources.Project.build(Project.java:88)

            at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:192)

            at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:134)

            at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:429)

            at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)

            at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

 

  • 0
    TI__Guru**** 173310 points

    I've seen the message "error occurred while traversing resources" once or twice and think I was able to resolve it by opening the project in a new clean workspace. Please try the troubleshooting steps described here with respect to cleaning workspace or trying a new one: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE

    Are you using the latest version v4.2.3? If not, I would also suggest updating to this version (via Help->Software Updates->Find and Install) or just downloading and installing the full image for 4.2.3 in a separate location from your current installation. That way you can have both versions to test out side by side. The full image for 4.2.3 can be downloaded from http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_4_Downloads

  • 0 in reply to AartiG
    Intellectual 255 points

    Thanks Aarti, for the suggestions.  I'm using 4.2.2, so if things still aren't working after re-creating the workspace, I'll try that.

  • 0 in reply to Matthew Waddell
    Intellectual 255 points

    Recreating the workspace didn't seem to have any affect.  Taking my modified projects and workspace, and trying to build them with ccs4.2.3 also caused the build manager to crash (same error and stack trace).  I'll try starting over again with ccs4.2.3 from the beginning: modify each project to use the 6.0.8 cgt.  The procedure I followed involved adding a separate build configuration to each project so that the legacy toolchain is used to build.  We've seen a number of issues with the build manager when it is given projects that have multiple build configurations, so perhaps this is a related issue.  I'll try reducing the number of build configurations so that the projects only contain the one that specifies cgt 6.0.8.

  • 0 in reply to Matthew Waddell
    Intellectual 255 points

    I've had some luck getting the projects to completely build by removing all but one build configuration, and removing all build dependencies.  I then tried adding the build dependencies back and everything seems to still be working.  Still sort of scratching my head as to what the problem is (could have been).  Next I suppose I'll add the build configurations back and see if everything continues to work.  I wonder if there was some sort of corruption in the project files(?)  Have there been any reports of this sort of thing?

  • 0 in reply to Matthew Waddell
    TI__Guru**** 173310 points

    I am glad to hear things are working now.

    Matthew Waddell said:
    I wonder if there was some sort of corruption in the project files(?)

    It is possible. More frequently we hear of workspace corruption, and usually cleaning the workspace or creating a new one resolves those issues. Unfortunately a project corruption is a bit more severe and seems to require recreating the project, which is understandably an inconvenience.