Pat Hickey

Currently CI doesn't do any publishing of artifacts, it just create some tarballs that the person on release duties (typically me?) downloads locally and uploads to the github release page....

If you want to use the minimal signal emulation, you'd invoke your clang like: ``` $ clang -D_WASI_EMULATED_SIGNAL -Wl,wasi-emulated-signal cp-skip-unused.c -o demo.wasm ``` Even with that minimal signal emulation, pthread.h...

This package started out before even llvm-dev packages included support for wasm32-wasi. In those days we used specific commits in the tree, experimental build flags, and even some out-of-tree patches...

Ah, yes, I did misunderstand. I agree we should not ship anything for working with llvm internals.

Thanks for the input, Daniel. I am not an npm user but it sounds like thats a good use case for this tool. Windows builds are currently blocked on a...

Looks like there was just a 9.0.1 llvm release, we'll upgrade to that for the next sdk release. hopefully that fixes windows. Just leaving this note so I get back...

Your understanding of the build is correct. This repo was developed out of necessity when we were trying to get wasi working before fixes were merged into LLVM and the...

@tschneidereit has done some work on using azure pipelines for this in wasi-libc. My understanding is that azure works quite well, and is free of charge. I don't think its...

Sounds good to me

@alexcrichton @peterhuene and I talked a bunch about how to solve this today: We decided that mangled strings with declared types are not viable for import functions, because a library...