Skip to main content

Specifying dependencies

This document only applies to applications that use .mtb files to specify their dependencies, not .lib files. To find information for applications that use .lib files, refer to an older version of this document.

Applications can share libraries. If needed, different applications can use different versions of the same library. Sharing resources reduces the number of files on your computer and speeds up subsequent application creation time. Shared libraries and versions are located in a "mtb_shared" directory adjacent to your application directories. You can easily switch a shared library to become local to a specific application, or back to being shared.

The Library Manager runs the make getlibs command to process the .mtb files, pull the libraries from the specified git repos, and store them in the specified location. The system also creates a file called mtb.mk in the application's libs subdirectory. The build system uses that file to find all the libraries required by the application.

The following shows the Library Manager for a typical PSOC™ Edge BSP. The key items are the lock symbols for libraries that are included because they are dependencies of other libraries. See Working with libraries for more details about using the tool.

The following concepts are key to understanding dependencies:

Last updated on