The domain ideas behind portable-python. Read these to understand why the build works the way it does.
- Portability - What "portable" means here, and how it is validated.
- Static linking - Why dependencies are compiled statically and paths relativized.
- Telltale detection - How the tool decides whether a library must be compiled or already exists.
- Folder masking - The macOS
/usr/localRAM-disk mask that prevents accidental dynamic linking. - Build layout - The
build/anddist/folder structure shared by every component. - ppp-marker prefix - The placeholder install prefix that fills in for
--prefixand is relativized for portable builds.