Closed sharpenedblade closed 4 months ago
I actually was thinking of making binaries that run only in macOS using pyinstaller.
It would make a .tar file in macOS itself then.
We cannot use python3 on macOS since it's not shipped with it. User will have to install python3. So, either ship a binary with macOS or use Linux to rename.
/usr/bin/python3
is from apple for me, it might be xcode dev tools but that can be installed in 1 command (xcode-select --install
).
We cannot use python3 on macOS since it's not shipped with it. User will have to install python3. So, either ship a binary with macOS or use Linux to rename.
/usr/bin/python3
is from apple for me, it might be xcode dev tools but that can be installed in 1 command (xcode-select --install
).
So we don't want user to install anything as far as macOS is considered.
Also, don't make the user install any additional software on macOS, that includes python3
Also, don't make the user install any additional software on macOS, that includes python3
I am going to try to embed python, but that makes the firmware script huge and it needs custom build steps which are very finicky. The python packaging ecosystem is a huge mess, and apple makes it very hard to distribute stuff on macos.
Also, don't make the user install any additional software on macOS, that includes python3
I am going to try to embed python, but that makes the firmware script huge and it needs custom build steps which are very finicky. The python packaging ecosystem is a huge mess, and apple makes it very hard to distribute stuff on macos.
Or we could just use Linux to rename. I had said I'll prefer macOS, but since embedding python is difficult, it's better to stay on Linux.
And if we want to embed, I guess pyinstaller is perfect for this scenario.
This just uses new mountpoints now, I will make a new PR with the python script running on macos
I fixed the requested changes.
It should work better now, and doesnt mess with mounts