diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-17 13:54:39 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-17 13:54:39 +0000 |
commit | 7f4e44f9469d8dcf6f95e07d0f5bb340f8830bfb (patch) | |
tree | 07741545f80a7f29822eb571d02db8dd0349674f /debian/control | |
parent | Adding upstream version 0.0~git20221206.8b7148f. (diff) | |
download | wasi-libc-7f4e44f9469d8dcf6f95e07d0f5bb340f8830bfb.tar.xz wasi-libc-7f4e44f9469d8dcf6f95e07d0f5bb340f8830bfb.zip |
Adding debian version 0.0~git20221206.8b7148f-1.debian/0.0_git20221206.8b7148f-1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'debian/control')
-rw-r--r-- | debian/control | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/debian/control b/debian/control new file mode 100644 index 0000000..0802b42 --- /dev/null +++ b/debian/control @@ -0,0 +1,35 @@ +Source: wasi-libc +Section: devel +Priority: optional +Maintainer: Debian Rust Maintainers <pkg-rust-maintainers@alioth-lists.debian.net> +Uploaders: + Ximin Luo <infinity0@debian.org>, + Fabian Grünbichler <debian@fabian.gruenbichler.email> +Build-Depends: debhelper-compat (= 13), clang-14, llvm-14 +Standards-Version: 4.6.1 +Homepage: https://github.com/CraneStation/wasi-libc +Vcs-Browser: https://salsa.debian.org/rust-team/wasi-libc +Vcs-Git: https://salsa.debian.org/rust-team/wasi-libc.git + +Package: wasi-libc +Architecture: all +Multi-Arch: foreign +Depends: ${misc:Depends} +Description: WASI libc implementation for WebAssembly + This is a work in progress. It's usable for many purposes, though the APIs + aren't stable yet. For example, this is used by the Rust compiler to build + its standard library for the wasm32-wasi target. + . + First, it's a usable libc. It builds a "libc" which can be used by compilers, + such as Clang 8.0, using the wasm32-wasi target. It's a work in progress, but + it is already sufficient to run basic programs. + . + Second, it's a "reference" implementation, which means the interfaces defined + here can be used by other tools and libraries, even if they don't use all the + actual implementations here. For example, we don't expect everyone will want to + use the exact malloc implementation provided here, but tools and libraries + using an ABI-compatible malloc interface will be able to interoperate + regardless of which actual implementation is used. + . + Third, it's an example showing the use of the WASI API. The libc functionality + is implemented using calls to WASI functions. |