-------------------------------------------------------------------------
|  +-  |    Shared(dynamic)       |   Static Library (Linkages)         |
-------------------------------------------------------------------------
|Pros: | less memory use          |   an executable, using own libraries|
|      |                          |     ,coming with the program,       |
|      |                          |   doesn't need to worry about its   |
|      |                          |   compilebility subject to libraries|
-------------------------------------------------------------------------
|Cons: | implementations of       |   bigger memory uses                |
|      | libraries may be altered |                                     |
|      | subject to OS  and its   |                                     |
|      | version, which may affect|                                     |
|      | the compilebility and    |                                     |
|      | runnability of the code  |                                     |
-------------------------------------------------------------------------

共享库最显著的优点是，不管有多少进程在使用这个库，内存中只加载一份代码。对于静态库，每个进程都有自己的代码副本。这可能导致严重的内存浪费。

静态库的一个优点是所有东西都捆绑到应用程序中。因此，您不必担心客户端系统上是否有正确的库(和版本)可用。

-------------------------------------------------------------------------
|  +-  |    Shared(dynamic)       |   Static Library (Linkages)         |
-------------------------------------------------------------------------
|Pros: | less memory use          |   an executable, using own libraries|
|      |                          |     ,coming with the program,       |
|      |                          |   doesn't need to worry about its   |
|      |                          |   compilebility subject to libraries|
-------------------------------------------------------------------------
|Cons: | implementations of       |   bigger memory uses                |
|      | libraries may be altered |                                     |
|      | subject to OS  and its   |                                     |
|      | version, which may affect|                                     |
|      | the compilebility and    |                                     |
|      | runnability of the code  |                                     |
-------------------------------------------------------------------------

在所有其他答案中，有一件事还没有被提及，那就是脱钩:

让我来谈谈我一直在处理的一个真实世界的生产代码:

一个非常大的软件，由>300个项目(visual studio)组成，主要构建为静态库，最后所有链接在一个巨大的可执行文件中，你最终会遇到以下问题:

-链接时间过长。你可能会有超过15分钟的链接，比如10秒的编译时间 -有些工具在处理这么大的可执行文件时是非常困难的，比如内存检查工具，它们必须检测代码。你可能会陷入被视为傻瓜的极限。

更有问题的是软件的解耦:在这个真实的例子中，任何其他项目都可以访问每个项目的头文件。因此，对于一个开发人员来说，添加依赖项非常容易;它只是包括标题，因为链接在最后将允许waws找到符号。它以可怕的循环依赖和完全混乱而告终。

使用共享库，需要做一些额外的工作，因为开发人员必须编辑项目构建系统来添加依赖库。我发现共享库代码往往提供更简洁的代码API。

简化:

静态链接:一个大型可执行文件 动态链接:一个小的可执行文件加上一个或多个库文件(Windows上是.dll文件，Linux上是.so文件，macOS上是.dylib文件)

A static library is like a bookstore, and a shared library is like... a library. With the former, you get your own copy of the book/function to take home; with the latter you and everyone else go to the library to use the same book/function. So anyone who wants to use the (shared) library needs to know where it is, because you have to "go get" the book/function. With a static library, the book/function is yours to own, and you keep it within your home/program, and once you have it you don't care where or when you got it.