Check for Required Tools: Depending on what you want to use ToolRunner for, various tools are necessary. This function runs a check on the available tools. Example output:

Figure 3.6. External Tools Check

In the top area, you can find the list of checked-for tools, grouped by use cases. Each use case consists of various tools. Tools may be necessary for more than one group. A use case can be run as long as all tools in it are available ("Ok").

UseCase and their tools (may be subject to changes)

Status

Description: Displays a brief description of what the specific tool is required for.

Typical User: Displays the typical user for this use case.

In the bottom area, you can find the overall results (including the required and found versions) and the URL and download URL to the software to help you install all necessary tools.

The Package Manager gives an overview over the available packages. They are separated into

The Package Manager does not handle the physical files; it manages only the search path for each package. Therefore, removing a package will only remove the package search path from the list.

Figure 3.7. Package Manager

To add your own packages, click Add User Packages. The standard file browser opens. Select and add folders or packages.

Folders are read recursively and all packages below them are automatically included. If you remove specific packages from a folder, you will be asked if you want to remove the complete folder from the list.

If a package with the same PackageIdentifier is found more than once, the last package found will overwrite the earlier packages. See the Package Structure documentation for details. These will be grayed out and marked with "Overwritten".

User Packages can be removed from the list. For this, select the user package and click Remove. You will be asked if you want to remove the package search path for the selected package. You can always re-add user packages.

Removes the files from the file list that are explicitly designated to be ignored for a build, typically listed per package under Configuration/Masterbuilder/MLAB_[PackageGroup_Package]/ignoredProfiles.txt.