Skip to content

Conversation

czarkoff
Copy link
Contributor

@czarkoff czarkoff commented Nov 1, 2015

In silent mode build infrastructure prints only short messages in format:

  TOOL  filename

and toolchain's warnings. In verbose mode it additionally echoes exact commands including all compiler and linker flags. By default baresip is built in silent mode (as before this commit); verbose mode can be set either by unsetting HIDE variable (running make HIDE=) or by setting V variable to any value (eg. make V=1 or make V=yes).

In *silent* mode build infrastructure prints only short messages in format:

  TOOL	filename

and toolchain's warnings.  In *verbose* mode it additionally echoes exact
commands including all compiler and linker flags.  By default baresip is built
in *silent* mode (as before this commit); *verbose* mode can be set either by
unsetting `HIDE` variable (running `make HIDE=`) or by setting `V` variable to
any value (eg. `make V=1` or `make V=yes`).
alfredh added a commit that referenced this pull request Nov 2, 2015
build infrastructure: silent and verbose modes
@alfredh alfredh merged commit 937581b into baresip:master Nov 2, 2015
abrodkin added a commit to abrodkin/re that referenced this pull request Jan 5, 2022
Inspired by baresip/baresip#87
to make it easier to see what's being done really during
build, if make run with "V=1".

This is especially important since we do some tricky
run-time checks for some components and the only way to find-out
what was detected and what not is to see full set of definitions
passed in CFLAGS.

Signed-off-by: Alexey Brodkin <alexey.brodkin@gmail.com>
abrodkin added a commit to abrodkin/re that referenced this pull request Jan 5, 2022
Inspired by baresip/baresip#87
to make it easier to see what's being done really during
build, if make run with "V=1".

This is especially important since we do some tricky
run-time checks for some components and the only way to find-out
what was detected and what not is to see full set of definitions
passed in CFLAGS.

Signed-off-by: Alexey Brodkin <alexey.brodkin@gmail.com>
abrodkin added a commit to abrodkin/re that referenced this pull request Jan 5, 2022
Inspired by baresip/baresip#87
to make it easier to see what's being done really during
build, if make run with "V=1".

This is especially important since we do some tricky
run-time checks for some components and the only way to find-out
what was detected and what not is to see full set of definitions
passed in CFLAGS.
abrodkin added a commit to abrodkin/re that referenced this pull request Jan 6, 2022
Inspired by baresip/baresip#87
to make it easier to see what's being done really during
build, if make run with "V=1".

This is especially important since we do some tricky
run-time checks for some components and the only way to find-out
what was detected and what not is to see full set of definitions
passed in CFLAGS.
sreimers pushed a commit to baresip/re that referenced this pull request Jan 7, 2022
Inspired by baresip/baresip#87
to make it easier to see what's being done really during
build, if make run with "V=1".

This is especially important since we do some tricky
run-time checks for some components and the only way to find-out
what was detected and what not is to see full set of definitions
passed in CFLAGS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants