You are not logged in.
Normally archlinux gets rid of static libraries, but I noticed that the wine package has +100 MiB of static libs in it.
I manually removed them and everything seems to work fine, so I'm not sure why they were kept around.
Offline
You are probably referring to the *.a files in /usr/lib/wine/x86_64-unix/ folder ?
The files in /usr/lib/wine/x86_64-windows all appear to PE versions, maybe the static ones are needed for applications that don't support PE ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Staticlibs are only removed if they have a dynamic (.so) counterpart.
https://gitlab.archlinux.org/pacman/pac … .sh.in#L38
The maintainer would need to manually clean these files up, assuming they genuinely aren't needed. Alternatively you can use pacman's noextract option to prevent these files being installed.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I don't think those static libs are needed at all, the alpine linux package of wine doesn't have them at all for example, even the static libs in the windows dirs are gone. They also strip the with windows dlls using x86_64-w64-mingw32-strip and i686-w64-mingw32-strip
I will open an issue about this in the repo.
Offline
https://gitlab.archlinux.org/archlinux/ … /issues/24
Well the reason is allow building with `winegcc`. Which I find odd, archlinux explicitly removes all static libs from llvm and that one is way more likely to fit that use case.
anyways, gonna be removing these manually.
Offline