From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: oss-tools@pengutronix.de
Subject: [OSS-Tools] [PATCH 1/3] meson: options: use defaults of type boolean for boolean options
Date: Mon, 12 Jun 2023 14:07:52 +0200 [thread overview]
Message-ID: <20230612120754.896995-1-a.fatoum@pengutronix.de> (raw)
From: Ahmad Fatoum <ahmad@a3f.at>
Building with newer meson versions alerts us that specifying defaults
with a string type for non-string types is deprecated. This type
confusion was not intentional, so fix that.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
meson_options.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meson_options.txt b/meson_options.txt
index f80643aa6c73..04d9854a4b1b 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -2,24 +2,24 @@
option(
'state-backward-compatibility',
type : 'boolean',
- value : 'false',
+ value : false,
description : 'barebox-state: when using the "direct" storage backend, keep the on-disk format readable by barebox <= v2016.08.0')
option(
'lock-device',
type : 'boolean',
- value : 'false',
+ value : false,
description : 'lock device node instead of creating lockfile in /run')
# build options
option(
'barebox-state',
type : 'boolean',
- value : 'true',
+ value : true,
description : 'Build barebox-state utility')
option(
'tests',
type : 'boolean',
- value : 'true',
+ value : true,
description : 'Enable/Disable test suite')
--
2.39.2
next reply other threads:[~2023-06-12 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 12:07 Ahmad Fatoum [this message]
2023-06-12 12:07 ` [OSS-Tools] [PATCH 2/3] test: add test case with non-existent /dev/file Ahmad Fatoum
2023-07-27 8:23 ` Roland Hieber
2023-06-12 12:07 ` [OSS-Tools] [PATCH 3/3] meson: set optimization level to -O2 by default Ahmad Fatoum
2023-07-27 8:23 ` Roland Hieber
2023-07-27 8:23 ` [OSS-Tools] [PATCH 1/3] meson: options: use defaults of type boolean for boolean options Roland Hieber
2023-08-01 10:10 ` Roland Hieber
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=20230612120754.896995-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=oss-tools@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox