library(3)

💖 NAME 💖

library — How to Build a Library 🎀 (this is from the avr-libc manual, section 3, bestie)

---

✨ Introduction ✨

Okay so, vibe check: do you keep rewriting the same functions over and over again? 😭 Like you literally copy-paste them from one project into the next? Would you lowkey love to cut down your maintenance overhead? Then bestie, it is TIME — you're ready to build your own library. 💅

Code reuse is a very laudable goal, no cap. With some upfront investment, you can save time and energy on future projects by having ready-to-go libraries just sitting there, waiting for you. 👑

This chapter describes some background information, design considerations, and practical knowledge that you will need to create and use your own libraries. It's giving foundational. 🦋

---

🔗 How the Linker Works 🔗

The compiler compiles a single high-level language file (C language, for example) into a single object module file. That's the whole job. One file in, one object module out.

The linker (ld) can only work with object modules to link them together. Object modules are the smallest unit that the linker works with — that's the entire relationship, that's the whole dynamic, periodt.

Typically, on the linker command line, you will specify a set of object modules (that has been previously compiled) and then a list of libraries, including the Standard C Library. The linker takes the set of object modules that you specify on the command line and links them together. Afterwards there will probably be a set of 'undefined references'. 😳

A reference is essentially a function call. An undefined reference is a function call, with no defined function to match the call. It's giving "texted but nobody answered". 📱💀

The linker will then go through the libraries, in order, to match the undefined references with function definitions that are found in the libraries. If it finds the function that matches the call, the linker will then link in the object module in which the function is located.

This part is important, bestie, do NOT skip it: the linker links in THE ENTIRE OBJECT MODULE in which the function is located. 🚨

Remember, the linker knows nothing about the functions internal to an object module, other than symbol names (such as function names). The smallest unit the linker works with is object modules. That's it. That's the whole thing. 🙈

When there are no more undefined references, the linker has linked everything and is done and outputs the final application. Slay. ✨

---

🎨 How to Design a Library 🎨

How the linker behaves is very important in designing a library. Like, it's the main character of this whole situation. 👑

Ideally, you want to design a library where only the functions that are called are the only functions to be linked into the final application. This helps keep the code size to a minimum. Tiny. Petite. 🧚

In order to do this, with the way the linker works, is to only write one function per code module. This will compile to one function per object module. This is usually a very different way of doing things than writing an application!

There are always exceptions to the rule. There are generally two cases where you would want to have more than one function per object module.

1. The first is when you have very complementary functions that it doesn't make much sense to split them up. For example, malloc() and free(). If someone is going to use malloc(), they will very likely be using free() (or at least should be using free() 😭). In this case, it makes more sense to aggregate those two functions in the same object module. They're a package deal, fr fr. 🫶
2. The second case is when you want to have an Interrupt Service Routine (ISR) in your library that you want to link in. The problem in this case is that the linker looks for unresolved references and tries to resolve them with code in libraries. A reference is the same as a function call. But with ISRs, there is no function call to initiate the ISR. The ISR is placed in the Interrupt Vector Table (IVT), hence no call, no reference, and no linking in of the ISR. 💀

In order to do this, you have to trick the linker in a way. 😈 Aggregate the ISR, with another function in the same object module, but have the other function be something that is required for the user to call in order to use the ISR, like perhaps an initialization function for the subsystem, or perhaps a function that enables the ISR in the first place.

---

🛠️ Creating a Library 🛠️

The librarian program is called ar (for 'archiver') and is found in the GNU Binutils project. This program will have been built for the AVR target and will therefore be named avr-ar. 🎀

The job of the librarian program is simple: aggregate a list of object modules into a single library (archive) and create an index for the linker to use.

The name that you create for the library filename must follow a specific pattern: libname.a. The name part is the unique part of the filename that you create. It makes it easier if the name part relates to what the library is about. This name part must be prefixed by 'lib', and it must have a file extension of .a, for 'archive'. The reason for the special form of the filename is for how the library gets used by the toolchain, as we will see later on. 👀

Note: The filename is case-sensitive. Use a lowercase 'lib' prefix, and a lowercase '.a' as the file extension. No uppercase shenanigans, bestie. 🙅‍♀️

The command line is fairly simple:

avr-ar rcs <library name> <list of object modules>

The r command switch tells the program to insert the object modules into the archive with replacement. The c command line switch tells the program to create the archive. And the s command line switch tells the program to write an object-file index into the archive, or update an existing one. This last switch is very important as it helps the linker to find what it needs to do its job. 🔥

Note: The command line switches are case sensitive! There are uppercase switches that have completely different actions. Do not play with them. 💀 MFile and the WinAVR distribution contain a Makefile Template that includes the necessary command lines to build a library. You will have to manually modify the template to switch it over to build a library instead of an application. Manual labor, unfortunately. 😔

See the GNU Binutils manual for more information on the ar program.

---

🌈 Using a Library 🌈

To use a library, use the -l switch on your linker command line. The string immediately following the -l is the unique part of the library filename that the linker will link in. For example, if you use:

-lm

this will expand to the library filename:

libm.a

which happens to be the math library included in avr-libc. Math? In MY avr-libc? It's more likely than you think. ✨

If you use this on your linker command line:

-lprintf_flt

then the linker will look for a library called:

libprintf_flt.a

This is why naming your library is so important when you create it! 🎀

The linker will search libraries in the order that they appear on the command line. Whichever function is found first that matches the undefined reference, it will be linked in. First come, first served, no takebacks. 💅

There are also command line switches that tell GCC which directory to look in (-L) for the libraries that are specified to be linked in with -l. 👑

See the GNU Binutils manual for more information on the GNU linker (ld) program.

---

okay that's the whole page bestie, you're literally a librarian now 🧚📚💖

This was the library(3) page from the avr-libc manual, Version 2.1.0, dated Sat Jan 29 2022. Bye bestie, go build something iconic! 🦋✨👑