If you do not want to create a manifest file for your custom libraries, then you must manually include the library and its dependencies in each application that uses the library. You can include the library several different ways, such as:
- git clone the version of the library that you want (or use some other revision control system) into the application's directory
- unzip an archive file of the library into the application's directory
- recursive copy the library into the application's directory
- modify the
SEARCHvariable in the application's Makefile to point to the library - add an mtb file to the deps directory for the library and run
make getlibs(requires that the library is in a Git repo)
For the first four methods, the library can go anywhere in the application's directory tree. Remember that if you put it in the libs directory it will not be checked into source control by default, so you will normally want put manually added libraries somewhere else.
If you use the mtb file (that is, the fifth method), there are two things to be aware of: the library will still not show up in the Library Manager; and latest locking will not be performed on that library so you should use a fixed version in the mtb file unless you want the dynamic update behavior.