Project Macros

From Texas Instruments Wiki
Jump to: navigation, search

This topic describes the various macros that are available for use within projects. They can be used when specifying build command or build options and in general are quite useful when trying to make projects portable and more maintainable.


Macro Description
${InputFileName}
Represents the input file name.
${InputFileExt} Represents the extension of the input file.
${InputFileBaseName} Represents the base name of the input file. That is the file name with an extension stripped.
${InputFileRelPath} Represents the input file path relative to the builder current directory.
${InputDirRelPath} Represents the input file directory path relative to the builder current directory.
${OutputFileName} Represents the output file name.
${OutputFileExt} Represents the output file extension.
${OutputFileBaseName} Represents the output file base name. That is the output file name with an extension stripped.
${OutputFileRelPath} Represents the output file path relative to the current builder directory.
${OutputDirRelPath} Represents the output file directory path relative to the current builder directory.
${ConfigName} Represents the name of a given configuration.
${ConfigDescription} Represents the description of a given configuration.
${BuildArtifactFileName} Represents the name of the build artifact.
${BuildArtifactFileExt} Represents the extension of the build artifact.
${BuildArtifactFileBaseName} Represents the base name of the build artifact.
${BuildArtifactFilePrefix} Represents the prefix of the build artifact.
${ProjName} Represents the name of a given project.
${ProjDirPath} Represents the absolute path of a given project.
${WorkspaceDirPath} Represents the workspace absolute path.
${DirectoryDelimiter} Represents the directory delimiter used on the system. That is the “\? for Win32 systems and the “/? for Unix-like systems. This could be useful, e.g. in the case a user needs the absolute path of an input file. The absolute path would be represented in the following way: ${CWD}${DirectoryDelimiter}${InputFileRelPath}
${PathDelimiter} Represents the default path delimiter used on the system to separate paths in the path environment variables. That is the “;? for Win32 systems and the “:? for Unix-like systems

This might be used in the environment variable definitions

${EclipseVersion} Represents the current Eclipse version.
${CDTVersion} Represents the current CDT version.
${HostOsName} Represents the operating system name on which eclipse is running.
${C2000_CG_ROOT} Installation folder of the C28x code generation tools.
${C5500_CG_ROOT} Installation folder of the C55x code generation tools.
${C6000_CG_ROOT} Installation folder of the C6x code generation tools.
${MSP430_CG_ROOT} Installation folder of the MSP430 code generation tools.
${TMS470_CG_ROOT} Installation folder of the ARM code generation tools.
${CCS_INSTALL_ROOT} Root installation directory of CCS. i.e. the directory installed in + /ccsv4 or /ccsv5
${CG_TOOL_ROOT} Installation folder of the currently selected code generation tools. Will be the same value as the matching <ISA>_CG_ROOT macro.
${CG_TOOL_SUFFIX} Contains the ISA of the currently selected code generation tools. i.e. 2000 for C2000.