Vendor things
This commit is contained in:
parent
5deceec006
commit
977e3c17e5
19434 changed files with 10682014 additions and 0 deletions
27
third-party/vendor/rustix/CONTRIBUTING.md
vendored
Normal file
27
third-party/vendor/rustix/CONTRIBUTING.md
vendored
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
# Contributing to rustix
|
||||
|
||||
Rustix is a [Bytecode Alliance] project. It follows the Bytecode Alliance's
|
||||
[Code of Conduct] and [Organizational Code of Conduct].
|
||||
|
||||
## Testing
|
||||
|
||||
To keep compile times low, most features in rustix's API are behind cargo
|
||||
features. A special feature, `all-apis` enables all APIs, which is useful
|
||||
for testing.
|
||||
|
||||
```console
|
||||
cargo test --features=all-apis
|
||||
```
|
||||
|
||||
And, rustix has two backends, linux_raw and libc, and only one is used in
|
||||
any given build. To test with the libc backend explicitly, additionally
|
||||
enable the `use-libc` feature:
|
||||
|
||||
```console
|
||||
cargo test --features=all-apis,use-libc
|
||||
```
|
||||
|
||||
Beyond that, rustix's CI tests many targets and configurations. Asking for
|
||||
help is always welcome, and it's especially encouraged when the issue is
|
||||
getting all the `cfg`s lined up to get everything compiling on all the
|
||||
configurations on CI.
|
||||
Loading…
Add table
Add a link
Reference in a new issue