feat: Implement cross-platform executable compilation and distribution (WIP) #451
Conversation
SethBurkart123
changed the title
build.sh
Outdated
|
|
||
| # 1. Clean previous builds | ||
| #echo "Cleaning previous builds..." | ||
| #rm -rf build dist |
There was a problem hiding this comment.
this should be uncommented
build.sh
Outdated
|
|
||
| # 2. Run PyInstaller | ||
| #echo "Building with PyInstaller..." | ||
| #pyinstaller exo.spec |
There was a problem hiding this comment.
where is the exo.spec file?
|
interesting approach! Just FYI, this is being worked on in #354. As far as I can tell (from looking at the package you generated in your releases on GitHub), this creates an executable along with a directory of supporting libraries needed to run it. PR 354 allows for a single file to be generated. |
I'm currently developing all of those changes locally, the disadvantage with generating a single file executable is quite large cold start times. It's definitely an option I have played with but on each execution all libraries need to be unpacked for it to run causing it to take a while to load up. |
|
I can probably contribute at least an aur package to this lol |
|
Might be worth making it a bit more client-servery though, I would like for this to be able to sanely run under systemd at least |
this would also be important if we were to make an optional frontend app as well. |
This work-in-progress pull request aims to transform exo into an easily installable executable for multiple platforms, streamlining the distribution process. Previous issue #334 was incorrectly closed by Github automatically.
Objectives:
Key improvements:
Related #302