Share via


Checking Dependencies

When you check dependencies, you determine and resolve the include dependencies of the components in your configuration. An include dependency is part of the definition of a component and specifies which other components must be present or absent for that component to work properly.

It is highly recommended that you check dependencies before you build a run-time image. This ensures that all of the components that are required or disallowed by the configuration are either included or not, as needed.

To check dependencies in a configuration

  1. In Target Designer, from the Configuration menu, choose Check Dependencies.

    Target Designer runs through each component in the configuration, determines whether its dependencies are satisfied, and displays the progress in the Dependency Check dialog box.

  2. When the dependency check is complete, in the Dependency Check dialog box, choose Close.

    Unresolved dependencies are displayed on the Tasks tab at the bottom of the Target Designer window. If Target Designer is configured to resolve dependencies automatically, the only unresolved dependencies on the Tasks tab are those that could not be resolved automatically. This is the case whenever there are several options for resolving a dependency.

  3. Complete each task on the Tasks tab either by resolving the dependency or by selecting the check box next to the task. For more information, see Manually Resolving a Dependency.

  4. To resolve any dependencies that were introduced during this process, repeat this procedure.

    The process of resolving dependencies often adds or disables components. If new components have dependencies of their own, a dependency check must be run again to resolve the dependencies that were introduced, and the check must be repeated until all dependencies are resolved. Similarly, if components are disabled, it is recommended that you run a dependency check to see if other components require these components to be enabled. If that is the case, you must determine which dependency can be left unresolved.

See Also

Dependency Checking | Include Dependencies