On 9 Aug 2023, at 07:47, Alexander Kanavin via lists.openembedded.org <[email protected]> wrote: >> Ideally we only want the verbosity when something goes wrong and meson ninja >> etc are good at that with their defaults perhaps that -v should be turned >> off by default as well > > Absolutely not. As someone who spends a lot of time fixing build and > runtime failures across all of oe-core I beg to differ. I want > verbosity all the time, everywhere. I also do not want to spend a > second figuring out how to switch it on (it's different everywhere > too), or to run another build just to get the verbose logs out of it.
Agreed with Alex. Unless Ninja is clever enough to emit the full log for _every_ build step that was involved in the failure, I definitely always want verbose logs. For what it’s worth this made me look at the recipe to see why it has to define do_compile, and I ended up extending meson.bbclass making this patch redundant. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185709): https://lists.openembedded.org/g/openembedded-core/message/185709 Mute This Topic: https://lists.openembedded.org/mt/100625045/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
