Brénainn Woodsend
Brénainn Woodsend
Sorry, I should have posted back here. See https://github.com/openwrt/docker/issues/112#issuecomment-1519099490. tl;dr is that even with the platform set properly, mips specifically has other issues that the rest of the architectures don't.
That's quite a neat way of doing it. I didn't realise qemu could run an initramfs.
Apparently on Debian/Ubuntu, running [this](https://github.com/openwrt/docker/pull/113/files#diff-19560c84548a42e84d08fea824c8d1aff05ede2f21a9cb0c5a18ca93791469feR286-R288) should let you run MIPS in Docker. On any other Linux distribution, [it's more complicated](https://github.com/openwrt/docker/pull/113#issuecomment-1548667952).
> I did need to patch PyInstaller's build setup since I see its build a non standard wheel path it broken so it's pulling PyInstaller from a custom GitHub branch...
Looks similar to #7578. [My unanswered question there](https://github.com/pyinstaller/pyinstaller/issues/7578#issuecomment-1512325709) applies here.
That would do.
Doesn't `mymodule` have a `__main__.py` submodule which runs the entry-point function? If it does, just run PyInstaller on that. If it doesn't then add it so that people who don't...
What if you get rid of the `-e` flag to pip? Editable installs for `pyproject.toml` based projects are known to be undiscoverable by PyInstaller (#7524).
That's expected and nothing to do with this issue then. If PyInstaller is not installed into the same environment as your packages then there's no way for it to find...
In the absence of any comment to the contrary, I'll assume that this is just #7524 again.