Using TestApe instrumenter with GCC

The gcc/g++ needs access to interface file and ld needs access to the library file. In addition certain system libraries are required. This is all taken care of by the package manager. To install TestApe on a Debian based system run

   dpkg -i testape_r556_i386.deb

   rpm -i testape-r556-2.i386.rpm

The package manager will put the binaries in /usr/bin, /usr/include, /usr/lib and the documentation and examples in /usr/share/doc/testape

If you want to do it manually, unpack the tar ball and put the instrumenter,interface and library in the proper directories. Remember to link to testape.a from /usr/lib/libtestape.a if you want to use -ltestape option.

The library and instrumenter will depend of the following libraries

   libstdc++.so.6
   libm.so.6
   libgcc_s.so.1
   libc.so.6

To use the instrumenter with the linux linker ld simply link with the testape library and invoke the instrumenter in front of the final linker command as shown in the examples below

 testape ld unit_a.o unit_d.o ad_test.o testape.a
 testape ld unit_a.o unit_d.o ad_test.o /path/testape.a

 testape gcc unit_a.c unit_d.c ad_test.c testape.a
 testape gcc unit_a.c unit_d.c ad_test.c -ltestape

If the libray is used together with tests written in C++, or if the tests are compiled with g++, the interface needs to be put inside a extern "C" declaration in order to be linkable with the C++ program.

Eventhough the instrumenter cannot autogenerate mocks for code that is written in C++, it is still possible to use the the framework to test the code. All mocks will have to be written manually.

For further information on TestApe with C++ see the forum at http://testape.com.