Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Take this as a rough proposal - I've read the docs so I know there are more requirements, but I don't feel like spending that much time on something that is maybe not considered for a reason. I have no issues with adding all that is required afterwards.
During configuration of many 3rd party projects I'm getting a lot of messages meant for developers of those libraries which can be silenced using
-Wno-dev
flag passed tocmake
. It cluttered the output so much I've started looking into it and spending better half a day on the issue I haven't found a way how to do it 'the right way'.There are
cmake_options
that can be passed tocmake.subproject
which I ended up with, but deprecated feature warning comes with it - still it's easier on the eyes than all the other unwanted output.I've look around the documentation, many issues, conversations and finally source code and I haven't been able to find such option. I've tried even to 'hack'
add_cmake_defines
with something like'DUMMYSTART=False -Wno-dev -DDUMMYEND' : false
but to no one's surprise, arguments are being passed properly 😄After all this I've come up with one solution myself and although it works, it is just that. Working proposal.
I don't know why it's not yet exposed, if there are some reasons to keep end user safe whatever just let me know. If it's something that could be implemented I'd gladly finish it, but I've come across the whole environment variables topic (python script to generate meson.options with resolved variables is working just great btw. but still), so I'm familiar with some forced limitations already. If this is one of those, feel free to close this PR.