• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 740 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.

Code Compose Command-Line Build Renders Java Exception

Alex Laird
Intellectual 320 points
Other Parts Discussed in Thread: CCSTUDIO

I am using a batch file to execute a CCS v4 build.  The batch file is show below:

:: (U) Set environment variables for the build
set CCS4_DIR=C:\Program Files\Texas Instruments\ccsv4\eclipse
set WORKSPACE_DIR=U:\My Program\My Workspace\
set PROJECT_NAME=MyProject

:: (U) Execute the Java build command for the RPI project the CCS workspace
"%CCS4_DIR%\jre\bin\java" -jar "%CCS4_DIR%\startup.jar" -data "%WORKSPACE_DIR%" -application com.ti.ccstudio.apps.projectBuild -ccs.projects %PROJECT_NAME% -ccs.configuration %1

The batch file renders the following output, and ultimately Java exception when executed with the command "MyBat Debug":

C:\>"C:\Program Files\Texas Instruments\ccsv4\eclipse\jre\bin\java" -jar "C:\Program Files\Texas Instruments\ccsv4\ecli
pse\startup.jar" -data "U:\My Program\My Workspace\" -application com.ti.ccstudio.apps.projectBuild -ccs.projects MyProject -ccs.configuration Debug

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Wed Aug 04 08:26:10 CDT 2010]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

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


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

--------------------------------------------------------------------------------
org.eclipse.core.internal.resources.ResourceException: Errors during build.
        at org.eclipse.core.internal.resources.Project.build(Project.java:91)
        at com.ti.ccstudio.apps.project.Build.buildProjects(Build.java:246)
        at com.ti.ccstudio.apps.project.Build.doRun(Build.java:104)
        at com.ti.ccstudio.apps.project.BaseHeadlessApp$1.run(BaseHeadlessApp.java:168)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719)
        at com.ti.ccstudio.apps.project.BaseHeadlessApp.internalRun(BaseHeadlessApp.java:166)
        at com.ti.ccstudio.apps.project.BaseHeadlessApp.run(BaseHeadlessApp.java:136)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:996)
        at org.eclipse.core.launcher.Main.main(Main.java:971)

Unfortunately, I tried recreating this exception from a fairly empty, default project, and it did not occur.  This means it must be something relating to the specifications of my project, but I am not able to share that project or any portions of its code here.  If you have any ideas what may cause an error such as this, it would be much appreciated so I could try it on my project.  I will continue to try to recreate this problem on a default project that I am able to share here.

  • 0
    TI__Guru*** 125430 points

    Can you share the compiler options and the linker options?  You can copy and paste from CCS:

  • 0 in reply to Brad Griffis
    Intellectual 320 points

    They were too long, and I can't do a screenshot, but here is the listings for you:

    Command: "${C5500_CG_ROOT}/bin/cl55"

    All options: -v5510 -g --define=DEBUG --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/include" --include_path="U:/My Program/Constants" --include_path="U:/My Program/My Workspace/My Code/Incl" --include_path="U:/My Program/My Workspace/My Code/Debug" --include_path="C:/Program Files/Texas Instruments/bios_5_41_02_14/packages/ti/bios/include" --include_path="C:/Program Files/Texas Instruments/bios_5_41_02_14/packages/ti/rtdx/c5500" -diag_warning=225 --ptrdiff_size=32 --memory_model=large -k

    Command line pattern: ${command} ${flags} ${inputs}

  • 0 in reply to Brad Griffis
    Intellectual 320 points

    This issue was making little to no sense to me, especially since I could not recreate it on any other project, in any other workspace, or on any other computer.  What I ended up doing was completely removing Code Composer Studio v4.1.2 (and deleting every folder trace of it on the system) and reinstalling CCS v4.1.3.  This resolved all problems ... Though I still don't really know what the problems were rooted in.  But I am now able to command-line compile!