Rok Mandeljc

PyInstaller's binary dependency analysis has always collected dependencies into top-level application directory, since that's the only location that is always guaranteed to be in the library search path. Only in...

Yeah, the described behavior matches what I would expect, as long as the `tdLib` package is not installed in site-packages (if it were, then directory preservation would also cause binary...

> > But to allow you to explicitly specify all binaries and avoid the duplication, the binary parent path preservation will need to be extended as I outlined earlier. >...

Can you open `build/testapp/Analysis-00.toc` for the CIPD-python build, and check where the python shared library was collected from? I suspect that the CIPD python doesn't actually have a shared library...

> Does this mean that PyInstaller has to search/hope that there is a `libpython.so` which corresponds to the Python instance currently executing PyInstaller? (And this heuristic got it wrong here?...

I suppose we could try detecting known problematic python builds based on sys.version, and raise an error immediately; i.e., something along the lines of "This version of Python is not...

Is the collected `libffi.7.dylib` signed at all? Because if this is an Anaconda environment, chances are that some libs are collected as DATA (as opposed to BINARY), and those do...

Well, a suggested "fix" would be to ditch anaconda for PyInstaller builds altogether... Because among other things, the symbolic links are not properly preserved and you likely end up with...

> 1. Yes, but if I make a new environment with just numpy and pyinstaller it no longer happens. So if you create a minimal conda environment with just `numpy`...

An alternative solution (if @Korijn is fine with it) would be to remove the hook code and related entry-point from the `freetype-py` (essentially reverting #162), and I add the hook...