We recently migrated a C6455 project from 5.1 to 5.3 to be tool-compatible with the C6678 developers. Our software build correctly when done inside CCS, build our build PC (using batch builds) fails. Once the project is imported, the build fails on the clean operation. The problem seems to be related to some issue with the workspace since these batch builds use a different temporary space. We use a python script to do these batch builds.
The load command is build using:
eclipsec.exe -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data c:\users\dboles\appdata\local\temp\EvgDspBuildWorkspace-2c7xpe -import CommonDSP
The clean command (which fails) is
eclipsec.exe -nosplash -application com.ti.ccstudio.apps.projectBuild -data c:\users\dboles\appdata\local\temp\EvgDspBuildWorkspace-2c7xpe -ccs.projects CommonDSP -ccs.configuration Release -ccs.clean:
The errors in the ...\.metadata\.log are obscure as to the cause. A little editing to show all but the tracebacks:
!MESSAGE Indexed 'CommonDSP' (57 sources, 208 headers) in 47.18 sec: 23,649 declarations; 57,592 references; 6 unresolved inclusions; 2 syntax errors; 1,410 unresolved names (1.71%)
!SESSION 2013-01-31 13:13:01.683 -----------------------------------------------
eclipse.buildId=I20120608-1200
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application com.ti.ccstudio.apps.projectBuild -ccs.projects CommonDSP -ccs.configuration Release -ccs.clean
Command-line arguments: -os win32 -ws win32 -arch x86 -application com.ti.ccstudio.apps.projectBuild -data c:\users\dboles\appdata\local\temp\EvgDspBuildWorkspace-trogpi -ccs.projects CommonDSP -ccs.configuration Release -ccs.clean
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!MESSAGE An error occurred while automatically activating bundle com.ti.common.project.core (1015).
!MESSAGE An error occurred while automatically activating bundle org.eclipse.core.resources (688).
!MESSAGE An error occurred while automatically activating bundle org.eclipse.cdt.core (639).
We start out loading CCS 5.2.1 but got upgraded when starting CCS. However, the 5.2.1 version was also failing.
We could reload CCS 5.1 if necessary but I am not sure we will be successful.