-
Notifications
You must be signed in to change notification settings - Fork 40
Difference between this plugin and linuxdeployqt #36
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
Comments
@probonopd could you bring some light to this issue? :) |
linuxdeployqt is older, and is based on macdeployqt (a part of Qt). It focuses on being simple, and has no plugins and little configurability. linuxdeploy is a complete rewrite, has a plugin architecture and more configurability. It is faster and more powerful, but also more complex. |
linuxdeploy-plugin-qt is first and foremost a standalone deployment system for apps' Qt dependencies, such as Qt plugin libraries, QML files etc. It is designed to work together with linuxdeploy, which does the heavy lifting of deploying the app itself and its direct library dependencies along with desktop files, icons and other things an AppImage/AppDir generally needs, the plugin amends the things linuxdeploy already deployed then. linuxdeploy with the Qt plugin are faster, provide more features and overall are easier to use, they provide a meaningful logging system and make debugging easy. |
Has your question been answered satisfyingly, @bugwelle? |
My bad, sorry. Forgot to answer. Yes, my question has been answered. But it may be worth to add a note about this in this project's README because I'm sure that I'm not the only one to be confused. π Thanks. |
Oh, didn't see that. Thank you π |
I may not call it the successor yet, but if you ask me... go with linuxdeploy, much more modern, faster, well tested. |
I've been using linuxdeploy-plugin-qt for more than a month now for nightly versions of MediaElch (switched from linuxdeployqt). export QML_SOURCES_PATHS="${PROJECT_DIR}/src/ui"
# Run linuxdeploy with following settings:
# - use qt plugin => so that Qt libraries are bundled correctly
# - use checkrt plugin => we use C++14 which requires libstdc++-6 which is not available on older systems
# this plugin bundled these newer libraries as well
# - use appimage plugin => create an appimage file (essentially just bundles the appdir)
"./linuxdeploy-x86_64.AppImage" --appdir appdir \
--desktop-file appdir/usr/share/applications/MediaElch.desktop \
--plugin checkrt \
--plugin qt \
--output appimage
Didn't hear complaints from users, yet. So I assume it's working just fine π |
Cool. Does the checkrt plugin work well for you? It's pretty... alpha... |
Kind of... Not worse than before. But because of gstreamer issues, etc., I wouldn't call MediaElch's AppImage stable. |
Oh, that's great to hear, would you want to collaborate on fixing the GStreamer issues? We know there's potential for linuxdeploy plugins that shall properly bundle GStreamer, and I'd like to see what you're doing to bundle them and how we could generalize that and make it another plugin. Please consider joining #appimage on Freenode, where we could talk about this. Meanwhile, please see linuxdeploy/linuxdeploy#80 for more information. Oh, by the way, I've listed your project in the READMEs of linuxdeploy, linuxdeploy-plugin-checkrt and awesome-linuxdeploy as a user of our tools. Please feel free to proofread and improve the texts. By the way, your script still says linuxdeployqt and also has a few workarounds that are no longer needed. I might consider sending a PR, but so far it looks good. |
Sure. But to be honest: I don't even know what part of MediaElch requires gstreamer (probably ffmpeg or mediainfo?). So there's a lot of new information in areas I've never touched. :)
Thanks. Now I've got no choice but to make MediaElch's AppImage stable :P
Oh, didn't notice that. Thanks. π |
Hi,
I was just wondering: What's the difference between linuxdeploy (+ this plugin) and linuxdeployqt?
Their names are quite similar but their usage is quite different. I couldn't find an answer to this, yet.
A short note in
README.md
would be helpful :)Regards,
Andre
The text was updated successfully, but these errors were encountered: