Rok Mandeljc

> So we better fix the --onefile behavior I would say, WDYT? Actually, both paths (for `onedir`and `onefile`) are incorrect. I think I have figured it out, and this is...

> Do you want me to try your branch on it? @BoboTiG if you want to do some testing, here's a branch that implements a proof-of-concept for a more proper...

I think that's an unforeseen side effect of #6218. Can you try to specify `STRIP` environment variable with path to the `strip` executable from the toolchain that you use (it...

Hmm, actually, I just noticed you're using PyInstaller 4.5.1, so your problem cannot be caused by #6218... But the problem is very likely incompatibility between `/usr/bin/strip` and the output of...

> for clarity I am on a mac with BigSur 11.6 and using a venv trying to target arm64 If you're trying to build macOS arm64 executable, you can use...

> do I need to run pyinstaller on an arm system for it to work? I thought the purpose of building the bootloader was for cross compatability Even if you...

> @rokm I spent a lot of time reading the documentation and that information was never clear IMO. You stated it very clearly, I think it should be in the...

Works as expected here with MSYS2 MinGW 64-bit prompt, so this might be specific to your environment... Can you verify which python executable you are using and where pyinstaller shim...

Yeah, that's normal if those DLLs are not in the PATH when Dependency Walker was launched. The idea is to get the list of first-order dependencies for further investigation. But...

> Then I noticed (by using pyi-archive_viewer) that there is no 'gi._gi' entry in the PYZ-00.pyz archive file (inside the build dir)... Maybe is this the issue? No, the `gi._gi`...