aboutsummaryrefslogtreecommitdiffstats
path: root/testing/icdiff
diff options
context:
space:
mode:
authorMinecrell <minecrell@minecrell.net>2020-01-06 18:46:39 +0100
committerLeo <thinkabit.ukim@gmail.com>2020-01-18 20:43:01 +0100
commit298e20d04fdbc33fc32a0388f645ca02e1fa3961 (patch)
tree53dd09e8b79ea225853413f97febbcba808563aa /testing/icdiff
parentc1263f4682a2c8adc48b7f19fc89483ca56603f7 (diff)
downloadaports-298e20d04fdbc33fc32a0388f645ca02e1fa3961.tar.bz2
aports-298e20d04fdbc33fc32a0388f645ca02e1fa3961.tar.xz
main/mesa: consolidate subpackages
Mesa uses so-called "megadrivers" to link multiple drivers into one shared library. Essentially there are only 4 distinct shared libraries built: - libmesa_dri_drivers.so ("classic" DRI drivers) - libgallium_dri.so (Gallium DRI drivers) - libgallium_drv_video.so (Gallium VAAPI drivers) - libvdpau_gallium.so.1.0.0 (Gallium VDPAU drivers) - (Note: Vulkan drivers are all built separately) These shared libraries are then hard-linked for each driver (i965, radeon, freedreno, ...). The APKBUILD attempts to create minimal packages by splitting the drivers into separate subpackages. Unfortunately this has exactly the opposite effect in this case. Instead of preserving the hard links with one large Mesa package, we copy the same shared library over and over again into separate subpackages. This causes significant overhead for storing all the apk packages, but also when installing multiple drivers on one system. The only useful separation we can make are the megadrivers themselves, i.e. one subpackage for each of the shared libraries mentioned above.
Diffstat (limited to 'testing/icdiff')
0 files changed, 0 insertions, 0 deletions