Editing Shared library (section)

== Library types ==
A program that is configured to use a library can use either [[Static linking|static-linking]] or [[Dynamic linker|dynamic-linking]]. Historically, libraries could only be static.<ref>{{Cite web |date=2018-10-25 |title=Difference between Static and Shared libraries |url=https://www.geeksforgeeks.org/difference-between-static-and-shared-libraries/ |access-date=2025-02-02 |website=GeeksforGeeks |language=en-US}}</ref> For static-linking ([[.lib]]), the library is effectively embedded into the programs executable file, while for dynamic-linking the library can be [[Load time|loaded]] at [[Runtime (program lifecycle phase)|runtime]] from a shared location, such as [[System file|system files]].

A program requires a [[compiler]] and [[Linker (computing)|linker]] step to access a library. In static-linking, those references are fully resolved at compile-time,<ref>{{Cite web |last=Microsoft |date=2021-10-29 |title=Walkthrough: Create and use a static library (C++) |url=https://learn.microsoft.com/en-us/cpp/build/walkthrough-creating-and-using-a-static-library-cpp?view=msvc-170 |access-date=2025-02-01 |website=learn.microsoft.com |language=en-us |quote=Using a static library is a great way to reuse code. Rather than reimplementing the same routines in every app that requires the functionality, you write them one time in a static library and then reference it from the apps. Code linked from a static library becomes part of your app—you don't have to install another file to use the code.}}</ref> whereas in dynamic-linking those references are not fully resolved until runtime by the [[operating system]].