feat: Implement cross-platform executable compilation and distribution (WIP)

[SethBurkart123]

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:

• Create a comprehensive PyInstaller spec file to bundle all required dependencies
• Implement CI/CD workflows for automated executable builds
• Ensure mac builds work
• Ensure linux builds work
• Ensure windows builds work
• Conduct comprehensive cross-platform testing to ensure complete functionality
• Package the executable in an installation-ready format
• Develop scripts for submission to Homebrew

Key improvements:

1. Simplified installation process for end-users
2. Broader platform compatibility
3. Automated build and distribution pipeline

Related #302

[dtnewman]

this should be uncommented

[dtnewman]

where is the exo.spec file?

[dtnewman]

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.

[lgcyaxi]

Don't submit the .DS_Store file. Please add it to .gitignore

[SethBurkart123]

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.