• Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 565 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 5.5 Project Rename NullPointerException

Marshall Schiring
Intellectual 745 points
Other Parts Discussed in Thread: CCSTUDIO

I'm trying to port my legacy CCSv3.3 project to CCS Version: 5.5.0.00077. I did a File->Import with "Copy projects into workspace". Then I go into project explorer and rename the project and change any user variable path's to point to the new location. The project updates fine with no errors and still builds.

However, anytime the indexer is run (Right click project -> Index -> rebuild for example) I get the following error:

An internal error occurred during: "C/C++ Indexer".

Looking in the error log I have the following stack trace:

java.lang.NullPointerException
at org.eclipse.cdt.utils.EFSExtensionManager.getPathFromURI(EFSExtensionManager.java:109)
at org.eclipse.cdt.internal.core.settings.model.DescriptionScannerInfoProvider.getValues(DescriptionScannerInfoProvider.java:250)
at org.eclipse.cdt.internal.core.settings.model.DescriptionScannerInfoProvider.createScannerInfo(DescriptionScannerInfoProvider.java:205)
at org.eclipse.cdt.internal.core.settings.model.DescriptionScannerInfoProvider.getScannerInfo(DescriptionScannerInfoProvider.java:132)
at org.eclipse.cdt.internal.core.settings.model.DescriptionScannerInfoProvider.getScannerInformation(DescriptionScannerInfoProvider.java:106)
at org.eclipse.cdt.internal.core.settings.model.ScannerInfoProviderProxy.getScannerInformation(ScannerInfoProviderProxy.java:38)
at org.eclipse.cdt.internal.core.model.TranslationUnit.getScannerInfo(TranslationUnit.java:1043)
at org.eclipse.cdt.internal.core.pdom.indexer.ProjectIndexerInputAdapter.getBuildConfiguration(ProjectIndexerInputAdapter.java:157)
at org.eclipse.cdt.internal.core.pdom.AbstractIndexerTask.parseLinkage(AbstractIndexerTask.java:827)
at org.eclipse.cdt.internal.core.pdom.AbstractIndexerTask.runTask(AbstractIndexerTask.java:508)
at org.eclipse.cdt.internal.core.pdom.indexer.PDOMIndexerTask.run(PDOMIndexerTask.java:139)
at org.eclipse.cdt.internal.core.pdom.indexer.PDOMRebuildTask.run(PDOMRebuildTask.java:87)
at org.eclipse.cdt.internal.core.pdom.PDOMIndexerJob.run(PDOMIndexerJob.java:137)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

And finally the session data:

eclipse.buildId=M20120914-1540
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product com.ti.ccstudio.branding.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

I can rename my project back to the original name and the error disappears. Any help is appreciated!

  • TI__Guru*** 130875 points

    Hi Marshall ,

    have you tried the legacy import wizard?   Project->import legacy ccsv3.3 projects?  This is the better way to import older projects like this.

    Do you see this with all projects?  I ask because I just renamed a project and reindexing afterwards did not cause an issue.

    Best Regards,

    Lisa

  • in reply to Lisa TI
    Intellectual 745 points

    Lisa,

    Yes, using the legacy ccsv3.3 importer is exactly what I used. I am only doing one project at this time.

    If you are not having problems, it must have something to do with my project settings, my changes seem pretty minimal (and only necessary to get code to build) to this point.

    I did have to mess with some build variables because the CSL was not migrated (this seems normal). I found one variable, $SRC_ROOT, which pointed to my original location, which is actually quite annoying. I thought by copying into the workspace it would eliminate all dependencies on the original location. I removed this variable.

    Thanks for the quick reply.

  • in reply to Marshall Schiring
    TI__Guru*** 130875 points

    Hi Marshall,

    ok, I hope that helped.  The one thing was not able to test was whether a legacy imported project would cause me an issue.

    All the best with development.

    Best Regards,
    Lisa

  • in reply to Lisa TI
    Intellectual 745 points

    I'm kind of confused. Nothing has changed? I was just confirming that I was using the legacy import when I ran into this problem.

    Additionally I have found out that my .cproject file is almost 1 MB in size and I think this is causing extremely slow performance when trying to build or close the project settings dialog box.

    I'm not really impressed with this import tool because I feel like I'm having to go back and fix things I would expect the import tool to do for me. I think I'm just going to build the project from scratch and see where that puts me.