Tool/software: Code Composer Studio
CCS Version : 8.3.0.00009
I have 4 similar projects within the same workspace, they share many source files and build variants of the same thing.
I have modified the Project properties such that the compiler invocation is actually a batch file, which runs PCLint, then invokes the compiler.
This has been working for a year or so, but recently as I have made tweaks to the project and added source modules CCS has taken it upon itself to reset certain project properties, causing my build to fail. I have therefore regularly had to set them back to my preferred settings and all is well until the next time !
However, yesterday CCS ramped things up a notch, it has decided not to pass compiler switches and settings ( as setup in project properties ) as a long command line string, it now passes the name of a file instead ( -@"ccsCompiler.opt" ). To make matters worse the file doesn't include all the parameters I require. Also, of my 4 projects within the workspace, two still work fine, the other two have this problem, no amount of faffing from me seems to make a difference !
So, can you tell me why CCS has taken it upon itself to do this ? and is there any settings menu where I can set it back to what I want ?
The setting in question is :-
Project Properties->CCS Build->MSP430 Compiler
Command : "${CODE_CHECKER_DIR}/bin/CheckAndCompile.bat"
Command line pattern : ${command} ${CODE_CHECKER_DIR} ${CG_TOOL_CL} ${output} ${flags} ${inputs}
Above is my preferred setting, which now fails in two of the projects ( ok in the others ), if I change the "command" to the usual ${CG_TOOL_CL} it builds but obviously doesn't run PCLint.
Many thanks,
Andy
