Publish libpython for WASI

[assambar]

Is your feature request related to a problem? Please describe.

Allow people to extend python in WASI apps.

Describe the solution you'd like

Should be a fat libpythonXXX.a, which also includes all static libs it depends on.

Describe alternatives you've considered

No response

Additional context

No response

[brettcannon]

FYI I'm working on https://github.com/brettcannon/cpython-wasi-build to handle pure builds from the CPython code base which will include a zip file with all the build artifacts like libpython*.a.

[assambar]

@brettcannon this is great!

Your approach makes it easy to follow as it's self contained! I would love it if we're eventually able to reuse your work.
Will have to check on how easy it is to do that with GH actions locally.

Our approach is to use make with bash scripts for the sake of portability, but due to code reuse, the whole build process is harder to read through.

Out of curiosity, do you have any thoughts about the proper approach for linking to all the extra static libs needed by libpython?

We decided to combine them all into a fat libpython3.11.a, but we're still not convinced this is the right thing to do.
This is what I have in mind -

webassembly-language-runtimes/python/v3.11.1/wlr-build.sh

Line 105 in 723e48b

logStatus "Create libpython3.11-aio.a"

Also, decided to add -Wl,-z,stack-size=524288 -Wl,--stack-first -Wl,--initial-memory=10485760 to ldflags in the pkg-config file to help end users avoid stack overflow errors.

[brettcannon]

I would love it if we're eventually able to reuse your work.

I would love it if we're eventually able to reuse your work.

Already thinking about that. 😁 python/cpython#103065

Out of curiosity, do you have any thoughts about the proper approach for linking to all the extra static libs needed by libpython?

Nope as I have been worrying about getting that repo up and going (I'm still primarily focused on getting WASI to a tier-2 language for CPython so no one has to worry about it being broken). 😅 I think most people are manually listing the various .a and .o files at link-time.