chore: Build for riscv64gc #5204
Conversation
pavelzw
changed the title
| "aarch64-apple-darwin", | ||
| "aarch64-unknown-linux-musl", | ||
| "aarch64-pc-windows-msvc", | ||
| "riscv64gc-unknown-linux-gnu", |
There was a problem hiding this comment.
how did you choose the architecture abbreviation here? Why riscv64gc rather than (say) riscv64?
There was a problem hiding this comment.
Ah, I see from conda/rattler#1949 that you're following rust terminology? Can you add a comment about any/all this in conda-forge/conda-forge.github.io#1744? I'd like to avoid having different names for the same architecture in different places. I'm willing to be convinced that we should follow rust's naming if necessary, but by default I was expecting to use riscv64.
There was a problem hiding this comment.
C.f. also conda/conda-build#5884; I'd expect to be able to do
- if: riscv64
then:
- somethingin v1 recipes
There was a problem hiding this comment.
Hi @h-vetinari, FYI this is a cargo dist configuration file. The target triple is only relevant for the cargo build. Thus this has nothing to do with conda naming things.
|
@pavelzw What makes this still a draft? |
|
Where you able to test the |
|
@pavelzw do you care to add it to the install.sh script so the risc-v users can use that. |
4 participants
Description
with riscv support on conda-forge gaining traction (conda-forge/conda-forge.github.io#1744), we should also support it in rattler-based tooling.
Fixes #{issue}
How Has This Been Tested?
AI Disclosure
Tools: {e.g., Claude, Codex, GitHub Copilot, ChatGPT, etc.}
Checklist:
schema/model.py.