Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this PR is to get the
ring
crate compiling for*-sel4*
targets and to run its unit tests on those targets.First off, configuring upstream
ring
for certain baremetal targets is currently broken. For now, we will use coliasgroup/ring@10a2b3c, but I will propose a more suitable solution upstream.Second, the
test
crate (libtest
) that ships with the Rust toolchain requiresstd
. I've discovered that you can run unit tests written forlibtest
by substituting an API-compatible crate with something like :I also had to patch
ring
's tests to useno_std
.This PR uses this
ring
tree: https://github.com/coliasgroup/ring/tree/12eafcfa062e6713b6ee2123d90ca2a48bece768Only the first patch mentioned will be necessary for using
ring
in this project, the others are just for running its unit on*-sel4*
targets.