Closed KristofferC closed 3 years ago
It's quite easy to see these by using a program like windirstat, k4dirstat, disk inventory x etc:
Note that some packages are meant to be only BuildDependency
s and have only static libraries.
Can BB simply not ship the logs at all? For docs, perhaps a warning or audit step could be introduced, I imagine.
The log are sometime precious for debugging
Presumably we can store them elsewhere and not ship them to every user?
How about the import libraries on Windows (*.dll.a) ? Are they needed in some use scenario? My system has those 4% of packages+artifacts size. These are from artifacts directory with size > 1 MB
"libopenblas64_.dll.a" => 5660794
"libgeos.dll.a" => 3605936
"libcrypto.dll.a" => 2840812
"libipopt.dll.a" => 2191024
"libMagick++-6.Q16.dll.a" => 2030248
"libx264.dll.a" => 1474428
"libspatialindex.dll.a" => 1164128
"libxml2.dll.a" => 1069626
I think they're needed to build libraries that link to them
After https://github.com/JuliaPackaging/BinaryBuilder.jl/pull/755, uncompressed logs/
directory of OpenBLAS_jll
for x86_64-apple-darwin14-libgfortran4
in v0.3.9+4
is down to 464 KiB, from 7.8 MiB in v0.3.9+2
.
Feel free to close this whenever you think it is in a good enough state right now.
Here is a list of some builds that bundle:
Static libraries:
lib265
libcrypto
,libssl
libfdk-aac
libtiff
libvpx
libturbojpeg
,libjpeg
libvorbisenc
libvorbis
libzstd
libzmq
libmp3lame
libass
libbz2
libopenspecfun
Docs:
libxml2
(2.7 MB)libtiff
(1.4 MB)libogg
(570 kb)libvorbis
(840 kb)Logs:
FFMPEG
(3.2 MB)OpenBLAS
(8 MB)ImageMagick
(311 kB)Arpack
(463 kB)