Brénainn Woodsend

Probably easiest to switch to `pathlib.Path().glob()`? That implementation nicely avoids interpreting the path itself as a pattern.

This one I'm guessing? ```console > pacman -Fx '.*QtWebEngineProcess' extra/qt5-webengine 5.15.15-2 (qt5) usr/lib/qt/libexec/QtWebEngineProcess ``` So not even installed inside the Python environment...

FWIW, building on an up to date rolling distribution like Arch is generally a bad idea since all Arch packages will be built to expect very recent versions of glibc...

> "Your app should run in a bundle exactly as it does when run from source. " This is not true with the default value of the contents_dir. It appears...

Option 3 is the only one that is not invalid. This is not a PyInstaller specific thing (which is why it would be inaccurate for the docs to imply that...

Only in the sense that some application launchers (including those used by Windows and macOS desktops) set the working directory to that of the executable which meant that a relative...

Mind if I scrap the whole `makespec.make_variable_path()` functionality? The only substitution it knows is replacing the directory of PyInstaller itself which no one should have any reason to use?

That unhandled exception window is more just a placeholder for your own exception handling. For a production application, we'd rather that you do it yourself. Something along the lines of:...

`apt-get install` isn't going to help you here because you need zlib installed into the cross compiler's prefix rather than the system wide one. The problem is that that prefix...

`linux-mips` is a Debian image using glibc whereas OpenWRT uses musl so anything you build on that image will not run on OpenWRT. You'll need to pick a musl variant...