Ludovic Courtès <l...@gnu.org> wrote: > Hi, > > elaexuo...@wilsonb.com skribis: > > > When `strip-binaries?` is `#f` and a "debug" output is defined, said output > > remains empty. Instead, I expect "debug" to get populated with separated > > debug > > files. > > Hmm I see. The logic was different: #:strip-binaries? #f disables > stripping, but it doesn’t populate the “debug” output either. > > If you want to populate the “debug” output, you need to declare a > “debug” output in the package and keep #:strip-binaries? #t. > > (I can see arguments for and against both interpretations, but that’s > how it is currently.)
Oh. Blah. It was something obivous. Hehe. Thank you for cleaing up my confusion. I apparently misread `lower` from (guix build-system gnu), thinking it stripped the "debug" output if #:strip-binaries? is true. > [...] > > > If the above is correct, then would it make sense for --with-debug-info to > > also > > inject a "debug" output as needed? It looks like this would be pretty easy > > under guix/transformations.scm:transforma-package-with-debug-info. > > ‘--with-debug-info’ is meant to be used when you want to keep debug info > (and there’s no “debug” output). It seemed to me there’s no point in > having that debug info separate in that case, especially since you > wouldn’t be able to refer to it. > > HTH! Very! Much obliged.