Re: CVS commit: pkgsrc/lang/zig

[Greg Troxel <gdt%lexort.com@localhost>]

Adam <adam%netbsd.org@localhost> writes:

>>>> Log Message:
>>>> zig: make build verbose
>>> 
>>> Why?
>> 
>> The outout is too limited to spot any obvious errors while building,
>> it remains fairly limited when building with verbose output. This is
>> not to build zig itself to be verbose, just the log output. We do
>> this with a couple of other packages as well.
>
> In that case, you should use `make VERBOSE=1` and spare the others the details of the build. I prefer non-verbose builds, unless I'm trying to fix a problem.
>
> Thank you for understanding. :)

<individual hat>

I think it's a bug in cmake thinking to suppress the line of what
actually is built.   There's no reason to look at build output at all,
unless you want to know what it did, or if it didn't work.   So making
it non-useful by default, and making everybody learn N methods to make
it how it should be is massively unhelpful.

So I think we should remediate this cmake culture bug, just like we
remediate other bugs.

If people want to suppress build lines, I think it makes sense to have a
user-settable pkgsrc variable BUILD_VERBOSITY that says whether builds
should show compile lines or suppress them.  We can then map that to
various kinds of VERBOSE in various build frameworks.

sort of

  - quiet: don't print about individual files, just some % thing
  - brief: one word/line per file
  - traditional: the compile line, which might be invoking libtool
  - verbose: also tell libtool to print the line it executed

</>