This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
Add support for multiple targets #165
Labels
enhancement
New feature or request
Comments
Robbepop
added a commit
to wasmi-labs/wasmi
that referenced
this issue
Jul 22, 2022
* CI: Check that the no_std build is built without std ... by placing it on a target without an operating system. The test's scope is reduced from --workspace to --lib, as only that component (and its transitive dependencies) are expected to be no_std. Closes: #374 * CI: Install necessary target for verifying no_std * Make wasmi_v1 no_std, pull in alloc where used * CI: Extend no_std tests to the whole workspace Non-library components stay included (src/bin/instantiate.rs is the only offender), but now it covers wasmi_v1 as well. * fixup! Make wasmi_v1 no_std, pull in alloc where used * squash! CI: Install necessary target for verifying no_std Workaround-For: actions-rs/toolchain#165 * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Co-authored-by: Robin Freyler <[email protected]> * fixup! Make wasmi_v1 no_std, pull in alloc where used Cargo fmt run after accepting style suggestions Co-authored-by: Robin Freyler <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do the checklist before filing an issue:
actions-rsActions?If you think it's a problem related to Github Actions in general, use GitHub Community forum instead: https://github.community
Motivation
I have a larger embedded project that supports multiple boards (each with their own crate).
The build process uses cargo-make and supports multiple targets during a top-level build.
Currently I need the following targets for a successful build:
Along with x86_64-unknown-linux-gnu for unit tests.
It would be useful to specify all the needed targets as a list, just like the components field.
Workflow example
I have no preference of target vs. targets. targets is probably easier for backward compatibility.
The text was updated successfully, but these errors were encountered: