Configuration Files
Configuration files (ctc.ini) store compiler-specific settings and a connection string to the license used by Testwell CTC++.
- Comments, starting with an #
- Beginning of command blocks, with the name given in squared brackets
- Settings with the structure
PARAMETER = value - Environment variables starting with $, for example
$(CTCHOME)
Exemplary extract from ctc.ini
# Global (applicable on all supported compilers) default definitions: # (In a single compiler-specific definition block these may be overridden) # WARNING_LEVEL = warn TIMER = clock MISSING_DEFAULT_INSTR = ON # # Compiler-specific definitions: # [Microsoft Visual C++] #VC++ 6.0 compliant at least... COMMAND = cl # Intel compiler COMMAND + icl TYPE = compiler_linker PREPROC_C = %COMMAND% /E /nologo /D__CTC__ %FLAGS% %FILE% > %RESULT% PREPROC_CXX = %COMMAND% /E /nologo /D__CTC__ %FLAGS% %FILE% > %RESULT% RUN_BEFORE_ALL = RUN_AFTER_CPP = RUN_AFTER_INSTR = RUN_AFTER_COMP =
Command blocks
The term "command" refers to compilers and linkers, e.g. cl, link, gcc, ld, armcc, armlink. A
command is the entity ctc works with when called:
ctc options-to-ctc command options-and-arguments-to-commandctc needs to know the scope of the command (compile only / compile and link / link only) and some information about its options.
For a specific compiler or linker command in a ctc call, all settings from the corresponding blocks are used. The command blocks are identified by the name of the first block found for this command.
Testwell CTC++ is preconfigured for many compilers out of the box, and Verifysoft provides additional settings for several cross compilers.