-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Warnings as errors #938
Warnings as errors #938
Conversation
this one's failing with some kind of cmake error, but my changes to cmake were very minor... |
It's failing in glslang, it's possible the warnings as errors setting is being applied to a dependency that's building with warnings? |
ah that makes sense. should we pass a different set of flags to dependencies? or just only set this flag later? |
I think setting it later might work? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The suggested changes set the options in CMake instead of the environment. This stops the flags from propagating to vcpkg and breaking the dependencies.
ae82d68
to
c1d7315
Compare
c1d7315
to
9ac374b
Compare
9ac374b
to
7530499
Compare
okie dokie! just a few more errors: Windows (fixed):
Ubuntu 20.04, amd64 (fixed):
Ubuntu 22.04, aarch64 (fixed):
I'm not sure about the Window's issues. The second one is an issue in crashpad. I'll take a look at the third one. |
(fixed) new windows error:
offending lines:
|
(fixed) new linux issue inside crashpad? I don't think anything changed about the paths...
|
on the server, an interesting one from tbb (fixed):
for this one we might just have to add |
1f91808
to
96ff814
Compare
1b68ff5
to
223fa4a
Compare
223fa4a
to
695d5d1
Compare
success!! this is ready for testing and review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
All looks good, I have just one question about possible protocol change
Surprisingly I tested Interface from this version and it does seem to work on regular servers, but indeed if there's change in protocol it's best to target it to protocol_changes. |
yeah, the problem only affects tags, which no one is using I’ll retarget this, since I’m working on some other protocol changes, hopefully it won’t be too long before we can merge back to master |
retargeted to protocol_changes! this is ready to merge from my end if it looks good to everyone! |
c0ef3ac
into
overte-org:protocol_changes
Closes #930
Funding
This project is funded through NGI0 Entrust, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.