mirror of
https://github.com/kusti8/proton-native.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #271] How to bundle and distribute the app #185
Labels
No labels
bug
documentation
enhancement
libui issue
pull-request
question
wait for libui implementation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/proton-native#185
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sparkenstein on GitHub (Mar 5, 2020).
Original GitHub issue: https://github.com/kusti8/proton-native/issues/271
Not sure if I missed something from reading docs, but is there a way to bundle and distribute binaries? electron-builder can generate .AppImage, .snap etc. Can we build such packages? If we can, is there a way to cross-compile packages as well. I am really considering using proton native for a huge open source project. I left PySide2 (python QT official wrapper) exactly because there's no good way available for bundling and distributing.
I see in some issues that you are experimenting with pkg or nexe. How is the progress?
PS: apart from bundling I'd like to help in documentation, the current docs are not really helpful for new comers. Are you planning to fix them soon or let me know if I can be of any help
@alizahid commented on GitHub (Mar 14, 2020):
I believe Electron Builder also supports Proton Native; https://www.electron.build/configuration/configuration#proton-native
@kusti8 commented on GitHub (Mar 16, 2020):
As of v2 electron builder doesn't support Proton Native. Distribution is very tricky, but its not that high of a priority right now. I did get it to work with nexe: https://proton-native.js.org/#/packaging, but it isn't ideal. I want to keep on adding components. Feel free to contribute to the docs by just submitting a PR.
@IngwiePhoenix commented on GitHub (May 4, 2020):
#283 if you want a rough idea of what you could do.