In the Properties of each referenced library, define the behavior when being inserted in a project along with its parent library.
Consider whether a referenced library should be hidden (not visible in the ), or if it is useful to create a container library (a library project containing library references):
|
Hidden library |
Deactivate the visibility of the library in the below the parent library by selecting the option in the Properties dialog box. Thus, hidden libraries can be available in a project. |
|
Container library |
A container library (*_Cnt.library) is a library project which does not define modules, but references other libraries. With container libraries, the access to the modules of these libraries is simplified. Create a container library if you want to include a set of libraries in a project at one time by including that container library. In this case, you can simplify the access to the modules of these libraries by making them top-level libraries. This allows you to leave out the namespace of the container library in the access path. To achieve this, select the option in the Properties dialog box. Select this option only for a container library. |
Interface libraries are referenced with the constraint . To achieve this, select the instead of a specific version when you include the library via the dialog box.
Container libraries are referenced with a constraint. To achieve this, select a specific version of the library in the dialog box.
Common libraries are referenced by a placeholder reference. This provides consistent relationships between different libraries. An update of an indirectly referenced library does not require modifications of each affected library but a modification of the placeholder definition.