From: Christian Lindig <christian.lindig@citrix.com>
To: Elliott Mitchell <ehem+xen@m5p.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@citrix.com>, "wl@xen.org" <wl@xen.org>,
"dave@recoil.org" <dave@recoil.org>
Subject: Re: [PATCH 2/2] tools/ocaml: Default to useful build output
Date: Mon, 20 Jul 2020 08:25:59 +0000 [thread overview]
Message-ID: <1595233559536.460@citrix.com> (raw)
In-Reply-To: <20200718033242.GB88869@mattapan.m5p.com>
________________________________________
From: Elliott Mitchell <ehem+xen@m5p.com>
Sent: 18 July 2020 04:32
To: xen-devel@lists.xen.org
Cc: Ian Jackson; wl@xen.org; Christian Lindig; dave@recoil.org
Subject: [PATCH 2/2] tools/ocaml: Default to useful build output
While hiding details of build output looks pretty to some, defaulting to
doing so deviates from the rest of Xen. Switch the OCAML tools to match
everything else.
Signed-off-by: Elliott Mitchell <ehem+xen@m5p.com>
---
Time for a bit of controversy.
Presently the OCAML tools build mismatches the rest of the Xen build.
My choice is to default to verbose output. While some may like beauty
in their build output, function is far more important.
If someone wants to take on the task of making Xen's build output
consistently beatiful, invite them to do so. Then call the police and
tell them you're being robbed.
---
tools/ocaml/Makefile.rules | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/tools/ocaml/Makefile.rules b/tools/ocaml/Makefile.rules
index a893c42b43..abfbc64ce0 100644
--- a/tools/ocaml/Makefile.rules
+++ b/tools/ocaml/Makefile.rules
@@ -1,17 +1,20 @@
ifdef V
- ifeq ("$(origin V)", "command line")
- BUILD_VERBOSE = $(V)
- endif
+ ifeq ("$(origin V)", "command line")
+ BUILD_VERBOSE = $(V)
+ endif
+else
+ V := 1
+ BUILD_VERBOSE := 1
endif
ifndef BUILD_VERBOSE
- BUILD_VERBOSE = 0
+ BUILD_VERBOSE := 0
endif
ifeq ($(BUILD_VERBOSE),1)
- E = @true
- Q =
+ E := @true
+ Q :=
else
- E = @echo
- Q = @
+ E := @echo
+ Q := @
endif
.NOTPARALLEL:
--
2.20.1
--
Acked-by: Christian Lindig <christian.lindig@citrix.com>
next prev parent reply other threads:[~2020-07-20 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 3:32 [PATCH 2/2] tools/ocaml: Default to useful build output Elliott Mitchell
2020-07-20 8:25 ` Christian Lindig [this message]
2020-07-20 8:38 ` Christian Lindig
2020-07-20 9:00 ` Paul Durrant
2020-07-20 9:24 ` Christian Lindig
2020-07-20 9:36 ` Edwin Torok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1595233559536.460@citrix.com \
--to=christian.lindig@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=dave@recoil.org \
--cc=ehem+xen@m5p.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.