Before instrumenting your application, configure your build system to be able to reach the API headers and libraries:
to your 32-bit
to your 64-bit
The default installation directory on Windows* OS is
Include the ITT API Header in Your Application
Add the following
statements to every source file that you want to instrument:
header contains definitions of ITT API routines and important macros which provide the correct logic of API invocation from a user application.
header defines many functions that are not covered in this document. However, Intel® GPA supports only the functions that are documented herein.
The ITT API is designed to incur almost zero overhead when tracing is disabled. But if you need fully zero overhead, you can compile out all ITT API calls from your application by defining the INTEL_NO_ITTNOTIFY_API macro in your project at compile time, either on the compiler command line, or in your source file, prior to including the
Static Library to Your Application
You need to link the static library,
, to your application. If tracing is enabled, this static library loads the ITT API data collector and forwards ITT API instrumentation data to Intel GPA.If tracing is disabled, the static library ignores ITT API calls, providing nearly zero instrumentation overhead.
If you are running Intel® GPA on a system with a legacy version of Microsoft* Visual Studio*, you must have the corresponding security updates installed to link against the dynamic version of the
Microsoft* Visual Studio* Version
Microsoft Visual Studio 2005
Microsoft Visual Studio 2008
If you do not want to update your version of Visual Studio, you must link the
static library to your application.
All ITT API functions with string arguments follow the Windows OS UNICODE convention, the actual function names are suffixed with A for the ASCII API and W for the UNICODE API. For example: