Home
How To...?Depending on the customer specific environment, Testwell CTC++ is used for many different testing scenarios, in several build environments, IDEs and tool chains. In this section, generic instructions are found as well as specific instructions for these kind of third party software.
WorkflowsMeasuring Code Coverage with Testwell CTC++ always works in three independent steps: instrumentation - testing - report generation. Depending on the environment, different ways to use the components of Testwell CTC++ are advantageous. They are described in these chapters.
Building an Instrumented Static Library The build target is not necessarily a complete executable, it can also be a (static) library. Testwell CTC++ can be used to instrument source files of a library.

Building an Instrumented Static Library

The build target is not necessarily a complete executable, it can also be a (static) library. Testwell CTC++ can be used to instrument source files of a library.

The instrumentation of the sources takes place normally and then the instrumented objects are put to the library with the library utility. The point to note is that the library will not contain the Testwell CTC++ run-time library. Thus, when you link the instrumented library to your final executable, you have to provide the Testwell CTC++ run-time-library at this stage.

A simple example:

Building the instrumented library

ctc cl /c file1.cpp
cl /c file2.cpp
ctc cl /c file3.cpp
lib /out:mylib.lib file1.obj file2.obj file3.obj

Building the client program

cl /Femyprog.exe clnt1.cpp clnt2.cpp clnt3.cpp \
    mylib.lib %CTCHOME%\Lib\ctcwin32.lib

Instrumenting a dynamic library (.dll at Windows, .so at Unix) is done in the same way as instrumenting an executable.