-
Notifications
You must be signed in to change notification settings - Fork 175
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
Document tier 3 platform support #255
Comments
The thumbv8 targets are all shipped in rustup by the way, so they should probably be moved to tier 2 |
@jonas-schievink Okay, do you want to create a seperate issue for that and I'll remove them from this list? |
Yup, opened #346 for that |
|
@flying-sheep Would you be willing to make a PR adding it? |
Actually I don’t even know what the checkmarks on the platform support page mean. That you can compile those things there? That there’s binary distributions of those things? Also does something other than the platform support page need to be changed? |
@XAMPPRocky Opened a draft #380 |
@flying-sheep A check means that you can build and compile that component for that architecture and it will work. So if something has ticked std and rustc, it means you can build std and rustc but not cargo for that platform. It’s probably not the most clear currently. |
Hmm, “The columns below indicate whether the corresponding component works on the specified platform” is sufficient information, but yeah, I think a bit more clarification wouldn’t hurt. |
I noticed |
I'm going to close since the platform support is no longer documented here. This is being tracked at rust-lang/rust#113739 and rust-lang/rust#116004. |
Tier 3 platforms
This is a tracking issue for adding documentation on the level of support a tier 3 Rust toolchain has. This is mainly "Can I use std on that platform?", "Can I build and run rustc on that platform?", and "Can I can build and run Cargo on that platform?".
aarch64-unknown-freebsd
aarch64-unknown-hermit
aarch64-unknown-netbsd
aarch64-unknown-none
aarch64-unknown-redox
aarch64-uwp-windows-msvc
aarch64-wrs-vxworks
armv4t-unknown-linux-gnueabi
armv6-unknown-freebsd
armv6-unknown-netbsd-eabihf
armv7-unknown-freebsd
armv7-unknown-netbsd-eabihf
armv7-wrs-vxworks-eabihf
hexagon-unknown-linux-musl
i686-unknown-dragonfly
i686-uwp-windows-gnu
i686-uwp-windows-msvc
i686-wrs-vxworks
mips64-unknown-linux-muslabi64
mips64el-unknown-linux-muslabi64
mipsisa32r6-unknown-linux-gnu
mipsisa32r6el-unknown-linux-gnu
mipsisa64r6-unknown-linux-gnuabi64
mipsisa64r6el-unknown-linux-gnuabi64
powerpc-unknown-linux-musl
powerpc-unknown-netbsd
powerpc-wrs-vxworks
powerpc-wrs-vxworks-spe
powerpc64-unknown-freebsd
powerpc64-unknown-linux-musl
powerpc64-wrs-vxworks
powerpc64le-unknown-linux-musl
riscv32i-unknown-none-elf
sparc64-unknown-openbsd
thumbv7a-pc-windows-msvc
wasm32-experimental-emscripten
x86_64-pc-solaris
x86_64-unknown-hermit
x86_64-unknown-l4re-uclibc
x86_64-unknown-uefi
x86_64-wrs-vxworks
The text was updated successfully, but these errors were encountered: