• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 2010 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.

URI is not absolute

Tim Redfern
Expert 1360 points
Other Parts Discussed in Thread: CCSTUDIO

I'm getting this error building a sample project in CCS 6.1.3.00033 for OSX:

Errors occurred during the build.

Errors running builder 'CDT Builder' on project 'MG_hello'.

URI is not absolute

 

In the .log we have:

!ENTRY org.eclipse.core.resources 4 75 2016-08-09 21:41:07.785

!MESSAGE Errors occurred during the build.

!SUBENTRY 1 org.eclipse.cdt.managedbuilder.core 4 75 2016-08-09 21:41:07.785

!MESSAGE Errors running builder 'CDT Builder' on project 'MG_hello'.

!STACK 0

java.lang.IllegalArgumentException: URI is not absolute

at java.io.File.<init>(File.java:416)

at com.ti.ccstudio.project.core.internal.build.CCSMakefileGenerator$1.visit(CCSMakefileGenerator.java:444)

at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:119)

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

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

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

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

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

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

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

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

at com.ti.ccstudio.project.core.internal.build.CCSMakefileGenerator.validate(CCSMakefileGenerator.java:438)

at com.ti.ccstudio.project.core.internal.build.CCSMakefileGenerator.regenerateMakefiles(CCSMakefileGenerator.java:379)

at com.ti.ccstudio.project.core.internal.build.CCSMakefileGenerator.regenerateMakefiles(CCSMakefileGenerator.java:367)

at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.performMakefileGeneration(CommonBuilder.java:1006)

at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.performPrebuildGeneration(CommonBuilder.java:873)

at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:748)

at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:510)

at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:459)

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

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

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

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

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

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

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

at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)

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

at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)

at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:405)

at org.eclipse.ui.actions.BuildAction$1.runInWorkspace(BuildAction.java:287)

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

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

 

  • TI__Guru**** 169754 points
    Hi,

    URI errors are usually malformed paths and/or filenames used to reference source files that are part of the project. These malformed paths prevent Eclipse/CCS from properly building the project.

    A definitive fix is to double-check all the paths to source files used - be especially careful about special characters or the presence of "C:\" in references and path variables to files.

    To check the source file references, right-click on a source file --> Properties --> Resource. The top of the box will show the path to the file and the resolved location (if the file is referenced via a Path Variable).

    To check the path variables, see the following reference:
    processors.wiki.ti.com/.../Portable_Projects

    Hope this helps,
    Rafael