Difference between revisions of "Distribution Files"

From STRIDE Wiki
Jump to: navigation, search
(Windows)
(Linux)
Line 63: Line 63:
  
 
  cd ~/stride
 
  cd ~/stride
  unzip ../STRIDE4.1_sdk-linux_4.1.xx.zip
+
  unzip ../STRIDE_sdk-linux_4.2.xx.zip
  
 
Once unzipped, files will have been installed under <tt>~/stride/SDK</tt>.
 
Once unzipped, files will have been installed under <tt>~/stride/SDK</tt>.

Revision as of 08:00, 14 September 2009

Overview

This article describes the packages to be installed on the software build system as part of your STRIDE target integration.

STRIDE Framework components are distributed as as set of compressed archives. Each archive package comprises functionally-related files.

Planning

  • tools
    • STRIDE Build tools
  • source files
    • STRIDE Runtime
    • Samples


Source Packages

These packages are distributed in source form.

STRIDE Runtime

This package contains ANSI C source files implementing the STRIDE Runtime. The runtime is the fundamental component of the STRIDE framework as it implements

  • Runtime APIs - providing test services to Test Units
  • An Intercept Module thread - upon which tests are run
  • Host transport services - enabling I/O between the target and host computer

An Operating System-specific Platform Abstraction Layer (PAL) is also required to map specific OS services to runtime system calls.

The runtime files are typically built into a library that is then linked with your target application. An OS-specific SDK package will contain the runtime sources along with an appropriate PAL, makefile to build the runtime library and other useful stuff.

Installation

The STRIDE runtime sources are distributed as a zip archive. To install, run an unzipping utility, maintaining the directory structure of the archived files. We recommend that you create a parent directory named "stride" into which you upzip the archive.

Note: All SDK packages include the STRIDE runtime. If you will be installing an SDK or have installed an SDK, explicit runtime installation is unnecessary.

Linux

The following installation example assumes that the runtime archive is located in your home directory and that the directory ~/stride exists. The version numbers in your archive file name may be different than those shown in the example.

cd ~/stride
unzip ../STRIDE_runtime-src_4.2.xx.zip

Once unzipped, files will have been installed under ~/stride/SDK.

Windows

The following installation example assumes the the runtime archive is located in your root directory and that the directory \stride exists. The version numbers in your archive file name may be different than those shown in the example.

The example uses the open source 7-Zip utility to unzip the archive.

cd \stride
"\Program Files\7-Zip\7z" x ..\STRIDE_runtime-src_4.2.xx.zip

Once unzipped, files will have been installed under \stride\SDK.

SDK (includes STRIDE Runtime)

An SDK is intended 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 integrate STRIDE with your target build.

For more information, see Sandbox Evaluation.

Installation

SDKs are distributed as zip archives. To install, run an unzipping utility, maintaining the directory structure of the archived files. We recommend that you create a parent directory named "stride" into which you upzip the archive.

Linux

The following installation example assumes that the SDK archive is located in your home directory and that the directory ~/stride exists. The version numbers in your archive file name may be different than those shown in the example.

cd ~/stride
unzip ../STRIDE_sdk-linux_4.2.xx.zip

Once unzipped, files will have been installed under ~/stride/SDK.

Windows

The following installation example assumes the the SDK archive is located in your root directory and that the directory \stride exists. The version numbers in your archive file name may be different than those shown in the example.

The example uses the open source 7-Zip utility to unzip the archive.

cd \stride
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_sdk-windows_4.1.xx.zip

Once unzipped, files will have been installed under \stride\SDK.

Samples

The Test Unit samples are a collection of source code that demonstrates the techniques for creating and executing test code on a target application, in both C and C++ development environments.

For more information, see Test Unit Samples.

Installation

The Test Unit samples are distributed as zip archives. To install, run an unzipping utility, maintaining the directory structure of the archived files. We recommend that you unzip the archive into a parent directory named "stride".

Linux

The following installation example assumes that the Samples archive is located in your home directory and that the directory ~/stride exists. The version numbers in your archive file name may be different than those shown in the example.

cd ~/stride
unzip ../STRIDE4.1_samples_4.1.xx.zip

Once unzipped, files will have been installed under ~/stride/Samples.

Windows

The following installation example assumes the the Samples archive is located in your root directory and that the directory \stride exists. The version numbers in your archive file name may be different than those shown in the example.

The example uses the open source 7-Zip utility to unzip the archive.

cd \stride
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_samples_4.1.xx.zip

Once unzipped, files will have been installed under \stride\Samples.

Binary Packages

Build Tools

The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process as part of your target build.

For more information, see Build Tools.

Installation

The build tools are distributed as zip archives on Windows and tgz archives on Linux. To install, run the appropriate decompression utility. It's recommended that these files be placed in a location that is on your PATH as they are run as part of an application build.

Linux

The following installation example assumes that the build tools archive is located in your home directory and that the directory ~/stride/bin exists. The version numbers in your archive file name may be different than those shown in the example.

cd ~/stride/bin
tar xvzf ~/STRIDE4.1_buildtools-linux-gcc41_4.1.xx.tgz

Windows

The following installation example assumes the the build tools archive is located in your root directory and that the directory \stride\bin exists. The version numbers in your archive file name may be different than those shown in the example.

The example uses the open source 7-Zip utility to unzip the archive.

cd \stride\bin
"\Program Files\7-Zip\7z" x \STRIDE4.1_buildtools-windows_4.1.xx.zip

Host Tools

The Host Tools package includes stride, the program you run on your host computer to run STRIDE tests on your target.

For more information, see stride.

Installation

The host tools package is distributed as a zip archive on Windows and a tgz archive on Linux. To install, run the appropriate decompression utility. It's recommended that these files be placed in a location that is on your PATH.

Linux

The following installation example assumes that the host tools archive is located in your home directory and that the directory ~/stride/bin exists. The version numbers in your archive file name may be different than those shown in the example.

cd ~/stride/bin
tar xvzf ~/STRIDE4.1_hosttools-linux-gcc41_4.1.xx.tgz

Windows

The following installation example assumes the the host tools archive is located in your root directory and that the directory \stride\bin exists. The version numbers in your archive file name may be different than those shown in the example.

The example uses the open source 7-Zip utility to unzip the archive.

cd \stride\bin
"\Program Files\7-Zip\7z" x \STRIDE4.1_hosttools-windows_4.1.xx.zip

Related Topics