Use cargo check -Zbuild-std instead of cargo miri setup

This should be more reliable (not building with `cfg(miri)` and more
accurately knowing whether a target supports std).

Known targets affected by this change:
- cygwin: should now build since it only breaks in `cfg(miri)`
- i686-pc-nto-qnx700: officially doesn't support std

closes #4
This commit is contained in:
nora 2025-07-05 14:21:26 +02:00
parent 0be7b4c981
commit df486c20f8
7 changed files with 85 additions and 68 deletions

View file

@ -15,10 +15,12 @@
codegen/linking of core works, but does not check whether std builds.
</p>
<p>
std is being built with <code>cargo miri setup</code>. If a target does
not support std, the std column represents core/alloc. This checks that
std builds (on targets that have it) but does not check whether
std is being built with <code>cargo check -Zbuild-std</code>. If a target
does not support std, the std column represents core/alloc. This checks
that std checks (on targets that have it) but does not check whether
codegen/linking works.
For older builds, <code>cargo miri setup</code> was used instead.
</p>
{% if let Some(core_broken) = core_broken %}
<p>