Studio:WorkspaceSetup.pl

The WorkspaceSetup script (found in frameworks directory of the STRIDE install location) provides a simple command line tool for creating workspaces from a Framework. This script requires perl for execution as well as the STRIDE Test Utilities.

Usage

Summary

 perl WorkspaceSetup.pl --framework=FrameworkFoo --workspace=MyNewWorkspace [--package=PackageBar]

Parameters

-w | --workspace = WorkspaceName

Specifies the new workspace to be created (the given name is used both as the name of the workspace and the new directory in which the workspace is created.

-f | --framework = TargetFramework

Specifies the STRIDE Target Framework to use when creating the workspace. As of this writing, STRIDE provides two basic frameworks: StrideLinux for a FedoraCore7 based target machine and StrideWindowsHost for a host-based simulation emulator. Customers may create additional frameworks and specify additional search paths for this script to use to locate the frameworks.

--frameworkdir = FrameworkSearchDirectory

Specifies an additional directory path to search for the specified framework. If the framework is not found in the default STRIDE frameworks directory, these directories will be searched. This option can be specified multiple times to add multiple directories to the framework search path.

-p | --package = PackageName

Specifies a Test Package to add to the workspace when it is created. If no packages are specified, the workspace will be created without any tests in it. This option can be specified multiple times to add multiple packages to the new workspace

-d | --packagedir = PackageSearchDirectory

Specifies an additional directory path to search for packages. For any package that is specified with the --package option, we first look in the packages directory in the STRIDE insatllation directory. If it is not found there, we will search in the location(s) specified by this option. This option can be specified multiple times to add multiple additional directories to the packages search path.

-a | --altconfig = configname

Some frameworks include minor variations to support slightly different hardware. In these cases, only the CommonSettings.pm and WorkspaceConfig.pm files need to differ. Framework authors can create different versions of these files in a single framework. These alternate versions should be named CommonSettings_[altconfig].pm and WorkspaceConfig_[altconfig].pm. Specifying the altconfig parameter to WorkspaceSetup will cause it to use these alternate configuration files when creating the workspace instead of the standard one.