Off-Target Environment: Difference between revisions
m (→Linux) |
No edit summary |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
Each SDK package targets a specific operating system | The STRIDE SDK is provided to be used primarily as an off-target evaluation or development sandbox. This allows you to use STRIDE in a small, controlled environment without needing to make changes to your target build. In addition, the SDK Makefile can serve as an example of the steps needed to add STRIDE instrumentation to your target build. | ||
Each SDK package has identical functionality, but targets a specific operating system. The SDK contains the following items: | |||
* STRIDE runtime source | * STRIDE runtime source | ||
| Line 7: | Line 9: | ||
* Compiler setting file for target processor | * Compiler setting file for target processor | ||
== Evaluation Steps == | |||
# Build the STRIDE runtime library | |||
# Build and connect to the target app with only the runtime | |||
# Build and test the target app with S2 diagnostic tests | |||
# Build and test the target app with the TestIntro sample | |||
==Building the STRIDE Runtime Library== | ==Building the STRIDE Runtime Library== | ||
Revision as of 15:43, 3 June 2009
Overview
The STRIDE SDK is provided to be used primarily as an off-target evaluation or development sandbox. This allows you to use STRIDE in a small, controlled environment without needing to make changes to your target build. In addition, the SDK Makefile can serve as an example of the steps needed to add STRIDE instrumentation to your target build.
Each SDK package has identical functionality, but targets a specific operating system. The SDK contains the following items:
- STRIDE runtime source
- PAL source for interface with the Target OS
- Makefile to build STRIDE runtime library, test and sample applications
- Compiler setting file for target processor
Evaluation Steps
- Build the STRIDE runtime library
- Build and connect to the target app with only the runtime
- Build and test the target app with S2 diagnostic tests
- Build and test the target app with the TestIntro sample
Building the STRIDE Runtime Library
Note: all Makefiles must be run with gnu make. For SDKs targeting OS's where this is not the standard make utility, an executable is supplied in the SDK's bin directory.
Linux
The Makefile assumes a gnu toolchain. (Other toolchains can be used; see the comments in the Makefile.)
- cd to ~/stride/SDK/Linux/src
- Build the library
make library
- The file ~/stride/SDK/Linux/out/lib/libstride.a will be produced
Windows
The Makefile assumes a Visual Studio toolchain. (Other toolchains can be used; see the comments in the Makefile.)
- If using Microsoft Visual Studio, open a Visual Studio command prompt to ensure that the compiler and linker are on your PATH.[1]
- cd to stride\SDK\Windows\src
- build the library using the supplied gnu make. (You will get Makefile errors if you use the default make.)
..\bin\make library
- The file stride\SDK\Windows\out\lib\stride.lib will be produced
Building the TargetApp
Verifying Host to Target Connectivity
Adding Diagnostic Tests
Adding Sample Tests
Makefile Targets
- all
- Builds the library target
- library
- Builds STRIDE runtime, producing stride.lib
- clean
- Deletes intermediate and target files
- testapp
- Builds an instrumented test application, TestApp.exe, using sources found in the sample_src directory
- database
- im
- daemon
Instrumenting Multiple Processes
Notes
- ↑ You can get a VS command prompt via the Start menu. Choose: Start -> All Programs -> Microsoft Visual Studio 200X -> Visual Studio Tools -> Visual Studio 200X Command Prompt