Should we merge `wasi-libc` into `wasi-sdk`?
abrown opened this issue · 3 comments
- it would allow us to test both projects more easily
- it would less coordination for creating a release (minor issue)
These are different projects.
People already having clang on their system don't need yet another LLVM copy.
And regarding releases, having distinct releases for wasi-libc and the wask-sdk package would make more sense. wasi-libc tags could be updated according to actual changes in the library, independently from LLVM releases.
OS package managers and toolchains shipping wasi-libc could ship the same versions rather than random git commits. And wasi-sdk could be updated according to LLVM releases.
I think the idea is that we would allow folks to build just the wasi-libc part of wasi-sdk. There would be no need to build clang or even fetch it (since its a submodule you could just skip that step).
There is precedent for maintaining project like this is single repo. For example the llvm-project contains clang, libc++, the linker and a libc all in one repo.
No