CCS3.3 initial build step macro access

Rob Hoeye15277

Other Parts Discussed in Thread: CCSTUDIO

Can anyone give me a list of the accessible macros that can be used in the command line of a projects Final build step, Initial Build step or a file specific Pre-build or Post-build step of a CCS3.3 project? Does http://processors.wiki.ti.com/index.php/Project_Macros apply to CCS3.3? My tests indicate not, first clue is the use of "{" in stead of "(" and the lack of $(Proj_cfg).

In the discussions I see reference to $(Proj_cfg) and (Proj_dir), see: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/32716.aspx and http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/32716/114429.aspx#114429

Is the file name (of the currently active source file) and include paths available as macros so I can craft a template pre-build step to call lint on a source file by file basis? Kind of like what was done in CCS4 in: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/52967/189808.aspx#189808

I would rather not have to create file specific pre-build step for each file by hand. The best would be that when I add a file it inherits a template prebuild step, if possible.
Even then, the available macros could eliminate the need to hand enter the include paths for each files prebuild step.Much like the discussion about this very thing on CCS4, http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/52967/189808.aspx#189808, however upgrading to CSS4.0 is not an option for my current project, but running LINT on all my source files is a requirement!

Thanks
Rob

over 15 years ago

0 Ki over 15 years ago

TI__Guru**** 479881 points

Rob Hoeye said:
Can anyone give me a list of the accessible macros that can be used in the command line of a projects Final build step, Initial Build step or a file specific Pre-build or Post-build step of a CCS3.3 project?

Some of the macros are described here, in addition to instructions on how to create your own:

http://focus.ti.com/general/docs/lit/getliterature.tsp?literatureNumber=spra913&fileType=pdf

This doc does not mention the file specific ones which are new to CCS 3.2+. See below for those.

Rob Hoeye said:
Does http://processors.wiki.ti.com/index.php/Project_Macros apply to CCS3.3? My tests indicate not, first clue is the use of "{" in stead of "(" and the lack of $(Proj_cfg).

That url is for the CCSv4 environment (hence the usage of "{"). v3 and v4 are very different environments.

Rob Hoeye said:
In the discussions I see reference to $(Proj_cfg) and (Proj_dir), see: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/32716.aspx and http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/32716/114429.aspx#114429

Those macros are supported in v3.

Rob Hoeye said:
Is the file name (of the currently active source file) and include paths available as macros so I can craft a template pre-build step to call lint on a source file by file basis? Kind of like what was done in CCS4 in: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/52967/189808.aspx#189808

These are file specific macros for v3.3 (there are new CCS 3.2 and greater):

$(Proj_cfg) : Current Active Configuration (Debug/Release or User Defined)
$(File_path) : Absolute path including file name i.e. (C:\CCStudio\myprojects\main.c)
$(File_name) : File name including extension i.e. main.c
$(File_basename) : File name without the extension i.e. main
$(File_dir) : Directory that stores file location i.e. C:\CCStudio\myprojects
$(Input_path) : input path as stored in the project file.
$(Input_dir) : directory of $(Input_path) as stored in project file

Code Composer Studio™︎

Code Composer Studio forum

CCS3.3 initial build step macro access