![]() One caveat of this approach is that we can’t use multiple versions of the same library in our program at the same time. Therefore, during runtime, the dynamic linker will look for the shared library specified in the soname field.įor that reason, we’ll be able to use different glibc versions in our program. The soname field specifies the filename for our target shared library. The linker will look for the soname field in the shared object and embed it in the resulting binary. So, in a way, we can have multiple versions of glibc on our machine and have a libglib-2.0.so link to a specific version. minor is the minor version of the API version, which indicates new features.major is the API version of the library - major upgrades possibly introduce backward incompatibility.name is the shared object (shared library) filename. ![]() The variables in the convention have different meanings: On Linux, the convention for naming shared libraries is lib.so. For instance, in the case of glibc, the libglib-2.0.so link under the /usr/lib directory will point to a particular version of glibc. The linker, during program compilation, looks for a soft link that links to a specific version of a library. It’s possible to have installations of multiple versions of the same shared libraries on a Linux machine.
0 Comments
Leave a Reply. |