-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow non-tier-one targets to be built #633
Conversation
This also removes the outdated x32 apple target
I didn't look at this PR too closely yet, but we'll also want to implement limits to avoid people building tons of targets. The limit should be overridable through the usual sandbox limits mechanism. |
Ah, good idea. Does 10 sounds like a reasonable limit? We currently build 6 so it's the same order of magnitude. |
Yeah that sounds fine. We'll also need to update the issue template for sandbox limit increases. |
Added a default limit of 10 targets and updated /about and the issue template. |
You didn't update the schema. |
I need to test locally that the schema change is right, one second. |
Co-Authored-By: Pietro Albini <pietro@pietroalbini.org>
256: Add embedded targets to docs.rs r=jonas-schievink a=hug-dev Some modules of this repo are gated by the various targets and hence docs.rs does not show the documentation for them! Like the Armv8-M ones for [example](#217 (comment)) and the `cmse` module. docs.rs now allows building for specific target and since [this PR](rust-lang/docs.rs#633) even for targets available via `rustup`! The `stm32f3_discovery` crate does it, look at ["Platform" on docs.rs](https://docs.rs/stm32f3-discovery/0.4.0/stm32f3_discovery/index.html). So I think it would be very neat to have on `cortex-m` and I proposing to add the following targets. The first one will show by default, I choosed the latest and greatest for that 😄 I tested locally with `cargo doc --target ...` for all of them. Co-authored-by: Hugues de Valon <hugues.devalon@arm.com>
Closes #563.
Waiting on #632.Merged.This uses rustup to install toolchains if they are not already installed. These toolchains will be removed on the next toolchain update, and will be downloaded again on request.
Only the last few commits are related to #563, all others are from #632.