-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
fails to compile against mutter 3.35.2+ (removed deprecated ClutterTexture) #659
Comments
If it's deprecated it could be easier to implement, i.e no conditional compilation. Because you shouldn't use deprecated code paths, and hopefully the alternate codepaths are viable in older versions of mutter. |
@worldofpeace At least one hopes for that to be the case. On the other hand, I don't take anything for granted when talking about libmutter anymore |
Also https://gitlab.gnome.org/GNOME/mutter/merge_requests/458 ClutterGeometry → graphene_rect_t |
https://gitlab.gnome.org/GNOME/mutter/merge_requests/935 |
For the people watching this issue, we don't target unreleased versions so no move will be done right now. |
@tintou I know, and that's completely understandable. I originally opened the ticket as a "beware, this change will be coming in a future GNOME release", and looking at the timing of future release dates, it will probably be in ubuntu 20.04 LTS (the base base for the next elementaryOS release?). And, for better or worse, I've switched all gala and greeter builds on fedora (both official packages and nightly builds) back to using the mutter 3.28 compat package for now ... which might break at any minute, since there's no guarantee that it will keep compiling and working on top of newer GNOME releases |
Fixed in master |
Looking at the NEWS for mutter 3.35.2
ClutterTexture
andClutterTextureClass
were removed.gala will probably have to be adapted to this change somehow ... at least according to the MR, it looks like alternatives are available:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/932
The text was updated successfully, but these errors were encountered: