-
Notifications
You must be signed in to change notification settings - Fork 243
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
Elfutils debug #601
Elfutils debug #601
Conversation
b5c6d13
to
89f0d7b
Compare
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is achieved by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
89f0d7b
to
ec44b45
Compare
Adding the debug info blows up the image size to 8GB. Since I haven't pushed the image, the build fails. |
That would be a quite stable download, no? That Is this the complete debuginfo for QT and elfutils, isn't it? I guess that, as QT is not compiled explicit, the debuginfo could be downloaded "somewhere", but as the elfutils is build on the container we'd need to also provide its debuginfo? |
On the image in the ci, which will make the ci super slow since it needs to download the hole image every time it runs. |
Isn't the distributed QT not enough? If it is then QT can be installed from the system package manager and the link to the matching download of debug infos can just be shared. If the system-provided QT (and/or rest) isn't usable it should be possible to:
|
can we instead output a separate |
Note: it should be possible to have a CI workflow building this, which is only manually triggered. |
I think I can create a workflow which is only run manually to create the image and upload it to github. This way the workflow could contain the debuginfo as an artifact. |
Yes, it just needs to be manually copied somewhere later on (ideally attached to a release) to allow downloading without login from a stable URL.
|
@lievenhey Looks like a perfect candidate to finish after #648 :-) ... .or should that be included there? |
solved in #648 |
This will finally close #560. I successfully tested it with a local running
debuginfod
instance. I didn't managed to get it running by using the ci bundle, because therun_debuginfod_in_docker.sh
didn't like mydebuginfo.zip
file.