-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.60.0: message()
does not accept bools anymore
#9436
Labels
Milestone
Comments
xclaesse
added a commit
to xclaesse/meson
that referenced
this issue
Oct 25, 2021
It has always been working even if not documented and there is no reason to not accept it. However, change "True/False" to "true/false" to be consistent with meson language. Fixes: mesonbuild#9436
Merged
Fixed here: #9447 |
xclaesse
added a commit
to xclaesse/meson
that referenced
this issue
Oct 26, 2021
It has always been working even if not documented and there is no reason to not accept it. However, change "True/False" to "true/false" to be consistent with meson language. Fixes: mesonbuild#9436
xclaesse
added a commit
that referenced
this issue
Oct 26, 2021
It has always been working even if not documented and there is no reason to not accept it. However, change "True/False" to "true/false" to be consistent with meson language. Fixes: #9436
Thanks :D |
nirbheek
pushed a commit
that referenced
this issue
Oct 28, 2021
It has always been working even if not documented and there is no reason to not accept it. However, change "True/False" to "true/false" to be consistent with meson language. Fixes: #9436
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When passing a boolean to
message()
, Meson throws an errorTo Reproduce
Write
message(true)
in your meson.build fileExpected behavior
Previous Meson versions converted booleans passed in
message()
to eitherTrue
orFalse
. This was useful, even if the docs say that you can only pass strings to it. I know this is technically the correct behaviour, but this is an unannounced breaking change. I would suggest reverting this change and mentioning the boolean conversion in the documentation. I believe this was introduced in 941b8a6 (edit: yes, reverting the change fixes the "issue")system parameters
Edit: found in marzer/tomlplusplus#121, see that issue for other details
The text was updated successfully, but these errors were encountered: