mirror of
https://git.proxmox.com/git/llvm-toolchain
synced 2025-06-12 21:37:23 +00:00
97d60707ed
Do a standalone build of libcxx/libcxxabi, for wasm32-wasi. libcxx
requires a libc, and thus this requires a new build dependency on
wasi-libc. wasi-libc is not currently available for wasm64, so limit the
build to wasm32.
This introduces two new binary packages:
- libc++-${LLVM_VERSION}-dev-wasm32
- libc++abi-${LLVM_VERSION}-dev-wasm32
There isn't currently a naming convention in Debian for WebAssembly. Use
a "-dev-wasm32" suffix, which makes it consistent with packages such as
"libc6-dev-i386" and "libstd-rust-dev-wasm32".
Given these builds are specific to WASI, it can be argued that the names
should be something like "-dev-wasm32-wasi", or simplified to
"-dev-wasi" (not very future proof) or "-dev-wasi32" (not something
upstream uses). Something to think through later on.
WebAssembly only supports shared linking, hence why we -dev packages are
provided, shipping development headers and static archives.
4 lines
162 B
Plaintext
4 lines
162 B
Plaintext
usr/lib/llvm-@LLVM_VERSION@/lib/wasm32-wasi/libc++.a
|
|
usr/lib/llvm-@LLVM_VERSION@/include/wasm32-wasi/c++/
|
|
usr/lib/llvm-@LLVM_VERSION@/include/wasm32-wasi/c++/v1/
|