{"id":64731,"date":"2022-05-31T09:00:41","date_gmt":"2022-05-31T09:00:41","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=64731"},"modified":"2022-05-31T09:00:41","modified_gmt":"2022-05-31T09:00:41","slug":"how-dynamic-linking-for-modular-libraries-works-on-linux","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=64731","title":{"rendered":"How dynamic linking for modular libraries works on Linux"},"content":{"rendered":"

How dynamic linking for modular libraries works on Linux<\/span>
\nJayashree Hutt\u2026<\/a><\/span>
\nTue, 05\/31\/2022 – 03:00<\/span><\/p>\n

\n
Register<\/a> or Login<\/a> to like<\/div>\n
Register<\/a> or Login<\/a> to like<\/div>\n<\/div>\n
\n

When you write an application using the C programming language, your code usually has multiple source files.<\/p>\n

Ultimately, these files must be compiled into a single executable. You can do this by creating either static<\/i> or dynamic<\/i> libraries (the latter are also referred to as shared<\/i> libraries). These two types of libraries vary in how they are created and linked. Both have advantages and disadvantages, depending on your use case.<\/p>\n

Dynamic linking is the most common method, especially on Linux systems. Dynamic linking keeps libraries modular, so just one library can be shared between any number of applications. Modularity also allows a shared library to be updated independently of the applications that rely upon it.<\/p>\n

In this article, I demonstrate how dynamic linking works. In a future article, I’ll demonstrate static linking.<\/p>\n

Linker<\/h2>\n

A linker is a command that combines several pieces of a program together and reorganizes the memory allocation for them.<\/p>\n

The functions of a linker include:<\/p>\n