-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
clang++-10 compiler warnings / formatting issues #192
Comments
Some of the formatting issues:
|
Another one
|
Python formatting:
|
|
Unfortunately it's going to be hard for me to fix these. I can only compile with MSVC and MinGW locally, and none of them give me any of these warnings... |
I just mentioned that in case you someday want to integrate the module into Godot :-) The above breaks the current Godot CI build. We're making a curated version of Godot 3.x because I think that unfortunately nobody really cares about the bugs anymore and the hyped 4.x will be useless for low-end hardware in schools or by children for years ... I kept my branch with your module that passed the ci here. You can have a look if you want. |
In fact I'm setting up CI currently, since I discovered how to use it to also make builds for multiple platforms earlier on a GDNative plugin. Going to fix the warnings there because they are treated as errors. So far I see it takes long to build (30 min for one platform without scons cache) but that's enough for me. Only problem so far is that the tests spin endlessly after hitting GLES3 failure (which works on the official Godot repo for reasons beyond my understanding). Also, this: godotengine/godot#36690
That would be cool, but I don't see this happening anytime soon.
You're maintaining a fork of 3.x with extra modules in it? |
Thanks, please keep going :-) Treating warnings as errors is generally a good idea. Some languages
I had no such problems, I cloned the Godot repo, activated the CI for my 3.2 rebased test-branch and deactivated some compiler warnings, since fixing of the old Godot code in so many places would make it unmaintainable against the official 3.2 tip. It uses the scons cache and usually runs faster than I can drink my coffee, honestly I don't care...
The new compilers are getting smarter to spot the issues. I'm not a C++ expert at all, but casting the value to something the same size or larger (which the Variant class supports) seems to fix the issue.
That's the plan. I currently only need a usable version of Godot for my CS courses that I am planning for next year. Version 3.x has better network support (multiplayer!) and you now, the kids love |
Just merged CI for Windows and Linux, which includes fixes for warnings. |
Warnings should be fixed now in master too. |
And they are back. Gonna fix them soon. |
This should be fixed now. There is a CI now so errors like this will get fixed soon after pushing to the repo, as it is impractical to test all compilers and platforms locally beforehand |
May show some unexpected code side effects. Godot 3.2 tip + Cory's FastNoise + modules/voxel/
scons use_llvm=yes use_lld=yes ... 2> >(tee ../log/xxx-$date.log >&2)
The text was updated successfully, but these errors were encountered: