You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the use-case for make installing a WASI build? It seems odd to do so since WASI is targeted towards server edge or embedded in applications. It certainly isn't usable out of the box as a system Python installation. I defer to Brett, but I would say make install is probably not supported for WASI.
Activity
emmatyping commentedon Aug 18, 2025
What's the use-case for
make installing a WASI build? It seems odd to do so since WASI is targeted towards server edge or embedded in applications. It certainly isn't usable out of the box as a system Python installation. I defer to Brett, but I would saymake installis probably not supported for WASI.oroppas commentedon Aug 18, 2025
While experimenting componentize-py against the recent version of CPython, I found it convenient to have the WASI target in the installation directory. Following https://github.com/dicej/wasi-wheels,
PYTHONPATHmust point to the WASI-target installation directory (e.g., https://github.com/dicej/wasi-wheels/blob/main/numpy/build.sh#L16 whereCROSS_PREFIXpoints to https://github.com/dicej/wasi-wheels/blob/main/Makefile#L3).will have
cross-build/wasm32-wasip1but it was not obvious to which directoryPYTHONPATHshould point.brettcannon commentedon Aug 18, 2025
So I have a couple ways to respond to this. 😁
--prefixset to some location where the contents get zipped up for distribution may be convenient.Pick your answer. 😉