You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using -Z build-std, cargo also enables you to pass various different flags which will specify the exact components to build, rather than all components. This can be useful if std isn't supported, but core and alloc are. Therefore, build-std could be provided as an array or bool (we shouldn't allow a table), and then passed transparent to -Z build-std.
Closes#896.
This is technically a breaking change because arbitrary strings passed
to the `CROSS_BUILD_STD` environment variable (e.g. `yes`) are now no
longer parsed as truthy values, but rather as a single crate name (or
multiple, if containing commas) to pass to `-Zbuild-std` (resulting in
e.g. `-Zbuild-std=yes`, which is invalid).
Behaviour remains the same when `CROSS_BUILD_STD` is set to `true`,
`false`, or a number that fits in an `i32`.
Checklist
Describe your request
When using
-Z build-std
,cargo
also enables you to pass various different flags which will specify the exact components to build, rather than all components. This can be useful ifstd
isn't supported, butcore
andalloc
are. Therefore,build-std
could be provided as an array or bool (we shouldn't allow a table), and then passed transparent to-Z build-std
.Describe why this would be a good inclusion for
cross
Allows more comprehensive use of
build-std
, without breaking old behavior.The text was updated successfully, but these errors were encountered: