docs/manual: document KBUILD_VERBOSE environment variable
PATCH 1/1 docs/manual: document KBUILD_VERBOSE environment variable
--- docs/manual/common-usage.txt | 3 +++ 1 file changed, 3 insertions(+)
docs/manual/common-usage.txt +3 -0
@@ -69,6 +69,9 @@ to +make+ or set in the environment: * +HOSTCXX+, the host C++ compiler to use * +HOSTCC+, the host C compiler to use +* +KBUILD_VERBOSE+, KBuild verbosity; it is essentially the same as specifying + +V=1+ in make arguments. If set, exports itself and +VERBOSE=1+ to all + subprocesses. * +UCLIBC_CONFIG_FILE=<path/to/.config>+, path to the uClibc configuration file, used to compile uClibc, if an internal toolchain is being built.
Signature · 1 line
2.31.1
PATCH 1/1 docs/manual: document KBUILD_VERBOSE environment variable
Anton, All,
Thanks for this contribution.
On 2021-04-19 19:03 +0300, Anton Leontiev spake thusly:
Quoted 10 lines
Signed-off-by Anton Leontiev <[email protected]>--- docs/manual/common-usage.txt | 3 +++ 1 file changed, 3 insertions(+)docs/manual/common-usage.txt +0
-0
docs/manual/common-usage.txt to +make+ or set in the environment: · line 74
Quoted 6 lines
docs/manual/common-usage.txt +3
-0@@ -69,6 +69,9 @@ to +make+ or set in the environment: * +HOSTCXX+, the host C++ compiler to use * +HOSTCC+, the host C compiler to use +* +KBUILD_VERBOSE+, KBuild verbosity; it is essentially the same as specifying + +V=1+ in make arguments. If set, exports itself and +VERBOSE=1+ to all + subprocesses.
The naming of the KBUILD_VERBOSE variable is just an implementation detail. That it has a similar purpose as a variable of the same name in Kbuild (the linux kernel buildsystem) is just happenstance.
Buildroot is not using Kbuild, nor is it even remotely based on Kbuild.
After discussing among maintainers, we decided that we did not want to officially expose that variable.
Regards,
Yann E. MORIN.
Quoted 10 lines
docs/manual/common-usage.txt +0
-0* +UCLIBC_CONFIG_FILE=<path/to/.config>+, path to the uClibc configuration file, used to compile uClibc, if an internal toolchain is being built.Signature · 6 lines
2.31.1 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 docs/manual: document KBUILD_VERBOSE environment variable
Yann E. MORIN <[email protected]>:
Quoted 9 lines
The naming of the
KBUILD_VERBOSEvariable is just an implementation detail. That it has a similar purpose as a variable of the same name inKbuild(the linux kernel buildsystem) is just happenstance.Buildroot is not using
Kbuild, nor is it even remotely based onKbuild.After discussing among maintainers, we decided that we did not want to officially expose that variable.
Then maybe it's better to rename this variable into something like BR2_VERBOSE?
Signature · 4 lines
Anton Leontiev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210428/4144b0bc/attachment.html>
PATCH 1/1 docs/manual: document KBUILD_VERBOSE environment variable
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Anton" == Anton Leontiev <[email protected]> writes:
Yann E. MORIN <[email protected]>:
Quoted 4 lines
The naming of the
KBUILD_VERBOSEvariable is just an implementation detail. That it has a similar purpose as a variable of the same name inKbuild(the linux kernel buildsystem) is just happenstance.
Quoted 8 lines
Quoted 5 lines
Buildroot is not using
Kbuild, nor is it even remotely based onKbuild.After discussing among maintainers, we decided that we did not want to officially expose that variable.
Then maybe it's better to rename this variable into something like
BR2_VERBOSE?
Perhaps. What is your use case for wanting to use an environment variable instead of the normal V=1 make argument?
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 docs/manual: document KBUILD_VERBOSE environment variable
Peter Korsgaard <[email protected]>:
Quoted 5 lines
Quoted 2 lines
Then maybe it's better to rename this variable into something like
BR2_VERBOSE?Perhaps. What is your use case for wanting to use an environment variable instead of the normal V=1 make argument?
I have a Jenkins job, which builds Buildroot. I want to add a job parameter to enable verbose output. Jenkins job parameters are automatically exposed as environment variables. So I've named it KBUILD_VERBOSE and that's all, I shouldn't change any commands.
Signature · 1 line
Anton Leontiev