Replies: 1 comment
-
|
Meson doesn't set a default C standard, so if you don't set one it should end up with whatever you're compiler defaults to. The ideal thing that a project does is set an appropriate default in their project(
'meson',
'c',
default_options : {'c_std' : 'c99'},
)You can also use Users can then override this with the Meson also is bit sloppy with differentiating our presentation of gnuXX extensions from MSVC cXX + Microsoft extensions. We would want to fix any of those if you findt hem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm exploring open-source projects and helping out and noticed one of the projects was using Libuv and they don't require GNU Extensions but just C11 standards for C. Meson seemed to be defaulting this to GNU11 on a windows based machine with the use of native command prompt for VS (MSVC).
Could I understand the behavior better as in, how a project, user(dev) or meson selects the C_std for projects? I want to encourage better portability with C11/C99 standards so any information does help.
Thank you lads!
Beta Was this translation helpful? Give feedback.
All reactions