Skip to content
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

Set warning level to 0 #80

Merged
merged 1 commit into from
Nov 11, 2024
Merged

Conversation

peter-urban
Copy link
Collaborator

@peter-urban peter-urban commented Nov 11, 2024

Related to #77

The reason why the meson test suit produces more errors than the makefile, is that the warning level was set to 2 (my fault). Explanation on meson warning levels:

Warning level 1 flags: -Wall
Warning level 2 flags: -Wall -Wextra
Warning level 3 flags:: -Wall -Wextra -Wpedantic

It may be good to discuss the desired warning flags in a future issue, but for now meson.build should just reproduce the same results as the makefile

Warning level 1: -Wall
Warning level 2: -Wall -Wextra
Warning level 3: -wall -Wextra -Wpedantic
@efiring
Copy link
Member

efiring commented Nov 11, 2024

Is there also an option for meson to provide more verbose (but not too verbose...) output?
Specifically, with make one can see the underlying command lines being run (e.g., the
gcc invocation with all the defines, flags, input files, etc. expanded out); I assume meson (or actually ninja)
is issuing similar command lines. It seems like it would be helpful for debugging to see them.
Or am I missing something about how meson works?

@efiring efiring merged commit ab3dbf6 into TEOS-10:main Nov 11, 2024
31 checks passed
@peter-urban peter-urban deleted the set_warning_level branch November 11, 2024 22:44
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