Using Libraries¶
Library repository
The library repository is the storage location on the development system for libraries and associated metadata. You can link any installed the libraries into your project by means of a library manager. Moreover, the libraries are installed with version management for easy library updates.
You can create and edit more repositories in addition to the preinstalled System repository.
See also
Library manager
The library manager manages the libraries that are linked into your project. It displays the libraries by the respective library types and properties. You can link more libraries from the library repository, remove them, or edit their properties.
The library manager can be inserted into the POUs view or the Devices view. In this way, a project can have one library manager per application and also one cross-application library manager in the POUs view. The library modules of the linked libraries in the POUs view can be called regardless of the application. The library modules of the linked libraries in the Devices view can be called in the respective application code only. Furthermore, placeholder libraries behave differently when downloading depending on their positions.
Libraries that are linked to a specific version in the project also have a placeholder for that version (placeholder library). You can define special placeholder resolutions. You can also use the placeholder resolution that is defined for a device in the device description or that is stored in the library repository for a library. The library manager notifies about the actual placeholder resolution and shows the version that is used when downloading an application (effective version).
If a library manager is linked cross-application in the POUs view, then you have global access to its contents. If placeholder libraries are linked, then only the placeholder resolutions in the device description or library repository are checked.
Normally, a library manager is linked in the Devices view. Then, only the application code below it calls the library modules. Moreover, the special placeholder resolutions are checked first for placeholder libraries. Only after that are the placeholder resolutions checked that are in the device description or that originate from the library repository.
See also