Desktop Installation: Difference between revisions
No edit summary |
No edit summary |
||
Line 26: | Line 26: | ||
Once unzipped, files will have been installed under the <tt>\stride</tt> directory. | Once unzipped, files will have been installed under the <tt>\stride</tt> directory. | ||
== Installed Directories and Files == | |||
Here is a quick orientation to the directories and files that are installed. | |||
===<tt>bin</tt>=== | |||
This directory contains the [[Build Tools|STRIDE Build Tools]] and the [[STRIDE Runner]]. | |||
The build tools are invoked early on in the target software build process to generate special STRIDE artifacts that are used in subsequent build steps and later when running tests against the target. In a sandbox installation, these files are needed on the host computer since this is where we are building the target application. In a production off-target environment, these files are needed only on the computer that performs the target software build. | |||
The [[STRIDE Runner]] is the program you use to run tests from the host. | |||
===<tt>Samples</tt>=== | |||
The Samples directory contains a number of subdirectories, each containing the source for a [[Test Unit Samples|sample test]]. | |||
===<tt>SDK</tt>=== | |||
This directory contains the subdirectories <tt>GRS</tt>, <tt>Runtime</tt>, and <tt>SLAP</tt>, which contain source code that comprises the STRIDE Runtime. | |||
In addition, there is a | |||
== Related Topics == | == Related Topics == |
Revision as of 22:08, 4 September 2009
To perform Sandbox Evaluation & Training, you need to install the STRIDE Framework package on your PC. Prior to version 4.1.02 (released in October 2009), the framework was distributed using a set of four separate archives. Starting with version 4.1.02 the framework is distributed as a single archive. For installation instructions for the earlier version, please see Package Installation for Version 4.1.01.
Installation Packages
Files are installed by unzipping the provided package to your PC. Packages are available targeting the following operating systems (your version number may be different than that shown):
- Windows XP
- STRIDE_framework-windows_4.1.02.zip
- Linux
- STRIDE_framework-linux_4.1.02.zip
Linux Installation
The following installation example assumes that the installation package 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_framework-linux_4.1.02.zip
Once unzipped, files will have been installed under ~/stride.
Windows Installation
The following installation example assumes the the installation package 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_framework-windows_4.1.02.zip
Once unzipped, files will have been installed under the \stride directory.
Installed Directories and Files
Here is a quick orientation to the directories and files that are installed.
bin
This directory contains the STRIDE Build Tools and the STRIDE Runner.
The build tools are invoked early on in the target software build process to generate special STRIDE artifacts that are used in subsequent build steps and later when running tests against the target. In a sandbox installation, these files are needed on the host computer since this is where we are building the target application. In a production off-target environment, these files are needed only on the computer that performs the target software build.
The STRIDE Runner is the program you use to run tests from the host.
Samples
The Samples directory contains a number of subdirectories, each containing the source for a sample test.
SDK
This directory contains the subdirectories GRS, Runtime, and SLAP, which contain source code that comprises the STRIDE Runtime.
In addition, there is a