Date: Wed, 27 Nov 2024 15:43:01 +0200
Mathias Stearn via SG15 <sg15_at_[hidden]> writes:
> But this gives a clean way for the compiler to introduce new files
> that the build system doesn't need to care about but are consumed
> by other operations (eg .dwo being used by gdb)
Unless the build system needs to install these .dwo files someplace
where gdb can find them, no?
I believe that will be the common theme: first it would seem the
build system doesn't need to care about some outputs (debug info,
SARIF files) but after a moment of reflection one realizes that
there are use-cases where the build system would need to be
involved.
> But this gives a clean way for the compiler to introduce new files
> that the build system doesn't need to care about but are consumed
> by other operations (eg .dwo being used by gdb)
Unless the build system needs to install these .dwo files someplace
where gdb can find them, no?
I believe that will be the common theme: first it would seem the
build system doesn't need to care about some outputs (debug info,
SARIF files) but after a moment of reflection one realizes that
there are use-cases where the build system would need to be
involved.
Received on 2024-11-27 13:41:57