Changeset 74390482 for general/genlib/genlib.xml
- Timestamp:
- 05/30/2005 09:33:35 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 8d77de6
- Parents:
- 893d9711
- File:
-
- 1 edited
-
general/genlib/genlib.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
general/genlib/genlib.xml
r893d9711 r74390482 15 15 duplicate code (and risk introducing bugs), it just has to call 16 16 functions from the libraries installed on the system. The most obvious 17 example of a set of libraries is <application>Glibc</application> which is 18 installed during the LFS book. This contains all of the 17 example of a set of libraries is <application>Glibc</application> which is 18 installed during the LFS book. This contains all of the 19 19 <application>C</application> library functions which programs use.</para> 20 20 21 <para>There are two types of libraries: static and shared. Shared libraries 21 <para>There are two types of libraries: static and shared. Shared libraries 22 22 (usually <filename>libXXX.so</filename>) are loaded into memory from the shared 23 23 copy at runtime (hence the name). Static libraries (<filename>libXXX.a 24 </filename>) are actually linked into the program executable file itself, thus 25 making the program file larger. Quite often, you will find both static and 24 </filename>) are actually linked into the program executable file itself, thus 25 making the program file larger. Quite often, you will find both static and 26 26 shared copies of the same library on your system.</para> 27 27 28 28 <para>Generally, you only need to install libraries when you are 29 29 installing software that needs the functionality they supply. In 30 the BLFS book, each package is presented with a list of 31 (known) dependencies. Thus, you can figure out which libraries you need to 32 have before installing that program. If you are installing something without 33 using BLFS instructions, usually the <filename>README</filename> or 34 <filename>INSTALL</filename> file will contain 30 the BLFS book, each package is presented with a list of 31 (known) dependencies. Thus, you can figure out which libraries you need to 32 have before installing that program. If you are installing something without 33 using BLFS instructions, usually the <filename>README</filename> or 34 <filename>INSTALL</filename> file will contain 35 35 details of the program's requirements.</para> 36 36 37 37 <para>There are certain libraries which nearly <emphasis>everyone</emphasis> 38 will need at some point. In this chapter we list these and some others and 38 will need at some point. In this chapter we list these and some others and 39 39 explain why you may want to install them.</para> 40 40
Note:
See TracChangeset
for help on using the changeset viewer.
