-
Notifications
You must be signed in to change notification settings - Fork 323
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
Compile error in Glaxnimate module #915
Comments
This is still a problem upstream: https://gitlab.com/mattbas/glaxnimate/-/blob/master/src/core/io/lottie/cbor_write_json.cpp#L20 Since we import this as a git submodule based on the latest release, I am going to turn off warnings as errors for anything but Debug builds. |
For now you can try building (requires a clean build directory) with |
Related to #915. I do not want bug reports about compile errors for code that we have little control over. Now, at least the user can
Since I'm running from a PKGBUILD arch script I couldn't figure out how to properly add the CXXFLAGS but changing the build type from Debug to Release fixes it. |
If this is a good enough answer I can close it. |
I just ran into this too on msys2 (Windows) for Shotcut daily. This happened because Arch and msys2 upgraded gcc from major version 12 to 13. Do not close; I want to track fixing this in a Debug build for a future version of glaxnimate. |
Reported upstream: https://gitlab.com/mattbas/glaxnimate/-/issues/603 |
Dan, |
Depends on what you mean by “OUR.” If you mean local then set the CMAKE_BUILD_TYPE=Debug |
I already make my local builds with CMAKE_BUILD_TYPE=Debug. That that does not catch them all for some reason (compiler versions, I suppose). I was thinking we could enable it for all these builds: Shotcut? Maybe someday in the future. I dunno. |
Ok but not the Docker build. I already have a local change yet to push to update the gitlab pipeline with more recent Fedora and turn on debug. That will catch more. But I don’t think we’ll ever catch them all. The case of Glaxnimate is more difficult as it is a git submodule, and we don’t yet have a way to set a separate build type for that module if that is even possible, which I doubt. |
The text was updated successfully, but these errors were encountered: