Building an Application That Supports Call Profiler Data Collection
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
To instrument an application for Call Profiler, you can set an environment variable that specifies the type of profiling probe to insert into the application, and then build the application. You can then use Call Profiler to collect data while the instrumented application runs.
To build an application that supports Call Profiler data collection
Open a command prompt build window.
In the PB IDE, to open a command prompt build window, from the Build menu, choose Open Release Directory.
To instrument the application with CallCAP probes, at the command prompt, type
set WINCECALLCAP=1.- or -
To instrument the application with FastCAP probes, at the command prompt, type
set WINCEFASTCAP=1.Note
FastCAP instrumentation is not supported on x86 microprocessors.
For information about the characteristics of CallCAP and FastCAP probes, see Characteristics of FastCAP and CallCAP Probes.
At the command prompt, type
set WINCEREL=1.If you set the WINCEREL environment variable, the Build tool copies the built application to the release directory.
At the command prompt, type
set RELEASETYPE=local.For information about the RELEASETYPE environment variable, see RELEASETYPE.
Navigate to the directory that contains the sources file for the application that you want to instrument.
At the command prompt, type
build -c.At the end of the build process, the build window displays a
BUILD: Donemessage, followed by a message that reports the number of files compiled.The file name and file name extension of the built application are determined by the values that you specified in the sources file in the directory containing the source code for the application. For more information about sources files, see Sources File.
See Also
Tasks
How to Use Call Profiler to Find Performance Problems
Concepts
Call Profiler Instrumented Module Building
Code Profiling