-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
pycairo failing appimage build #1500
Comments
I haven't tracked back the root cause to understand this for myself yet...but this was addressed for Flatpak: beeware/briefcase-linux-flatpak-template@dd1ad51?diff=unified&w=0 But even if you do those transformations for AppImage, you run in to why we had to lower our support for AppImage with Briefcase v0.3.16: As is laid out in that PR and related issues, the recent changes to PyGObject require a quite recent version of glib....but the whole premise of AppImage is building with older libraries for compatibility. So, for the time being, you can theoretically build AppImages using Briefcase and Toga on a sufficiently new-enough distro.....but the portability of that AppImage will likely be compromised. |
In terms of restoring what you had before, this should work: Update
|
As an alternative to specifying the support revision - modify the Dockerfile to install I've pushed a template branch that does this; if you add If someone can confirm this works for them, I'll backport this to the 0.3.16 template. It's also worth noting that the pining fix will only work with Toga <= 0.3.1. The next release of Toga requires a bug fix in PyGObject 3.46.0, so you can't satisfy the PyGObject and GlibC requirement on any published manylinux release. |
We have resolved this error:
via beeware/briefcase-linux-appimage-template#40. Until a new release is made for Python 3.12 from python-build-standalone, this fix only applies to Python 3.11 and older. Re-running And to reiterate, unless you use a much newer Docker base image than the default |
Describe the bug
The
-fdebug-default-version=4
seems to an options for clang, but not gcc. Not sure why pycairo panic on that.Steps to reproduce
Expected behavior
Build the image.
Screenshots
No response
Environment
Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: