Hi Sebastien, The commit 03b164f59ce40a3f5677b0588af2aee8d9697bf6 tools/makefile: silent all compile output
It has been reviewed and approved by several members https://github.com/apache/nuttx/pull/8378 Best regards Alin -----Original Message----- From: Sebastien Lorquet <sebast...@lorquet.fr> Sent: den 7 mars 2023 14:12 To: dev@nuttx.apache.org Subject: Re: Build system is broken Hi, Do your realize how counter-intuitive this is? I would have NEVER imagined that V=0 is not the exact contrary of V=1! Can this silent mode be made optional in a config setting please? It is really a non-feature. it's just a fantasy to please some committer, and should have never been accepted imho. When I want to contribute a one liner to submit a new flash chip I get forced to wait 48 hours for useless automatic tests that will not even compile my new code, and such profound changes gets integrated immediately with almost no review other than an automatic build. I know it because some commits do not have corresponding pull requests. This gives a feeling of double standard that does not seem in line with the inviolables of this project. Tomek: Thanks, but I am not interested in workarounds that look like "here is a way to avoid asking why a change was made". Sebastien On 3/7/23 13:45, Nathan Hartman wrote: > On Tue, Mar 7, 2023 at 7:23 AM Tomek CEDRO <to...@cedro.info> wrote: > >> On Tue, Mar 7, 2023 at 9:24 AM Sebastien Lorquet wrote: >>> No >>> V=1 is an entirely different thing. >>> I dont want to see the output mangled with tons of arm-none-eabi-gcc >>> command lines. >>> This stuff is another breakage >>> Sebastien > > > There is V=0 which gives the same output as before. > > It needs to be documented somehow, and in a way that people will see it, or > we will get a lot of complaints and questions about it after the next > release. > > Nathan >
