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.
Hello,
I have a strange behaviour on command line builds with CCSv4. Following the instructions from wiki I invoke the following command(s):
set CCS4_INSTALL_DIR=C:\Programme\Texas Instruments
set CCS4_WORKSPACE_DIR=D:\WorkingFolder\wks40
"%CCS4_INSTALL_DIR%\ccsv4\eclipse\jre\bin\java" -jar "%CCS4_INSTALL_DIR%\ccsv4\eclipse\startup.jar" -data "%CCS4_WORKSPACE_DIR%" -application com.ti.ccstudio.apps.projectBuild -ccs.projects MSG_AVC4_CCS40_TEST -css.configuration Release
The build runs, but there are 2 effects I don't understand:
1.) The build uses the current conigurations from the workspace, ignoring my option "-css.configuration Release". I checked, changing the workspace configurations the buld changes for the same command. Is something wrong with my command line?
2.) There is always a preceeding "Clean" step. Why?
I'm pretty sure the configuration names are correct (as default - "Debug" and "Release").
Any Ideas?
Kind regards,
Andi
--- console output ---
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Thu Nov 19 17:59:15 CET 2009]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
================================================================================
Pre processing...
================================================================================
Building...
--------------------------------------------------------------------------------
**** Clean-only build of configuration Debug for project MSG_C64P_CCS40 ****
C:\Programme\Texas Instruments\ccsv4\utils\gmake\gmake -k clean
"C:/Programme/Texas Instruments/ccsv4/utils/Cygwin/rm" -rf ./MSG_destroy.obj ./MSG_init.obj ./MSG_levelGet.obj ./MSG_levelSet.obj ./MSG_readFirst.obj ./MSG_readLast.obj ./MSG_readNext.obj ./MSG_readPrev.obj ./MSG_write.obj ./src/MSG_destroy.pp ./src/MSG_init.pp ./src/MSG_levelGet.pp ./src/MSG_levelSet.pp ./src/MSG_readFirst.pp ./src/MSG_readLast.pp ./src/MSG_readNext.pp ./src/MSG_readPrev.pp ./src/MSG_write.pp "MSG_CCS40.l64p"
' '
Build complete for project MSG_C64P_CCS40
**** Build of configuration Debug for project MSG_C64P_CCS40 ****
C:\Programme\Texas Instruments\ccsv4\utils\gmake\gmake -k all
'Building file: D:/WorkingFolder/TMS320C6000/Modules/MSG/src/MSG_destroy.c'
'Invoking: C6000 Compiler'
"C:/Programme/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6400+ -g --fp_mode=strict --define="_DEBUG" --include_path="C:/Programme/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="D:/WorkingFolder/TMS320C6000/Modules/MSG/C64P_CCS40/Debug" --include_path="C:/Programme/Texas Instruments/bios_5_41_00_06/packages/ti/bios/include" --include_path="C:/Programme/Texas Instruments/bios_5_41_00_06/packages/ti/rtdx/include/c6000" --include_path="C:/Programme/Texas Instruments/xdais_6_23/packages/ti/xdais" --include_path="C:/CCStudio/C6000/csl/include" --diag_warning=225 --sat_reassoc=off --fp_reassoc=on --mem_model:const=data --mem_model:data=far_aggregates --preproc_with_compile --preproc_dependency="src/MSG_destroy.pp" "D:/WorkingFolder/TMS320C6000/Modules/MSG/src/MSG_destroy.c"
'Finished building: D:/WorkingFolder/TMS320C6000/Modules/MSG/src/MSG_destroy.c'
' '
... and so on ....
Hi Andreas,
I would like to know if you got any answer or if you found yourself a way to Build without doing a clean before, via the command line.
Thank you.
For (1) I think you mean -ccs.configuration not -css.configuration. Probably just a typo, but it would explain why the option might be ignored.