Hi, On Wed, Aug 09, 2023 at 08:47:05AM +0200, Alexander Kanavin wrote: > On Wed, 9 Aug 2023 at 01:06, Khem Raj <[email protected]> wrote: > >>> I think this is only useful during debugging. So perhaps a comment to > >>> enable it is better than enabling it always. > >> > >> > >> The meson bbclass also compile with verbose so in my opinion it is better > >> to do the same > >> and make it consistent with the main systemd recipe > >> > >> meson_do_compile() { > >> meson compile -v ${PARALLEL_MAKE} > >> } > > > > > > 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.
I prefer verbose-by-default too. It is really annoying to investigate build race conditions in various CI environments without enough details in logs. Had to trigger a lot test builds because of this in the past. Same goes for testing. I know logging infra can be abused and on the limit too, but I don't think bitbake task log sizes increase that much compared to other stuff remaining in build tmp directories after builds. Cheers, -Mikko
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185693): https://lists.openembedded.org/g/openembedded-core/message/185693 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]] -=-=-=-=-=-=-=-=-=-=-=-
