Typically Debian packaging does this, so inspiration can start there; Windows may support PDB(?) files to offload debug data from binaries.
Either way, we can end up with less bloated program/library binaries without compromising debug-ability to troubleshoot end-user deployments better when needed.
Example from make install(-stripped) DESTDIR=... of the same build lets us gauge possible installation footprint savings from optionally installing debug data, about 2x on that platform:
$ du -ks ~/nut-inst/*ped
8150 /data/data/com.termux/files/home/nut-inst/stripped
14070 /data/data/com.termux/files/home/nut-inst/unstripped
Typically Debian packaging does this, so inspiration can start there; Windows may support PDB(?) files to offload debug data from binaries.
Either way, we can end up with less bloated program/library binaries without compromising debug-ability to troubleshoot end-user deployments better when needed.
Example from
make install(-stripped) DESTDIR=...of the same build lets us gauge possible installation footprint savings from optionally installing debug data, about 2x on that platform: