Repository navigation
Add generated toolchain, GPU and MPI pages and a Yggdrasil section - #15
Open
ViralBShah wants to merge 1 commit into
Open
ViralBShah wants to merge 1 commit into
ViralBShah wants to merge 1 commit into
Conversation
Merged
ViralBShah
force-pushed
the
vs/toolchains-page
branch
3 times, most recently
from
November 15, 2026 04:40
9807637 to
4e7f991
Compare
Pages generated at build time (utils.jl): - /toolchains/: every GCC, LLVM, Rust, Go and OCaml version, and the versions each platform supports, computed from BinaryBuilderBase with the same rules as choose_shards and the default LLVM - /gpus/: CUDA toolkits and their x86_64, ARM server and Jetson builds from Yggdrasil's platforms/cuda.jl, and NVIDIA, AMD, Intel, Apple and cross-vendor GPU libraries with versions from the General registry - /mpi/: MPI implementations and the platforms each is built for, from Yggdrasil's platforms/mpi.jl The homepage platform count, toolchain count, OS list and CPU list come from the same data. Homepage: - Fix the unclosed rows="27 attribute that dropped the player's poster - Split into BinaryBuilder features and a Yggdrasil section, with an icon traced from the Yggdrasil logo - Link features to the relevant documentation - Load the asciinema player only on the homepage - Add alt text to the feature icons Build: - Project.toml lists Franklin, NodeJS, BinaryBuilderBase, Downloads and RegistryInstances, with compat bounds - Build in a read-only job on pushes, pull requests, weekly and on demand; deploy from a separate job only from master - Update actions/checkout and julia-actions/setup-julia - Keep Project.toml, Manifest.toml and npm files out of the site - Remove the unused GitLab CI file and Franklin template assets Fixes #2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ViralBShah
force-pushed
the
vs/toolchains-page
branch
from
November 15, 2026 04:42
4e7f991 to
a302fa2
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #2.
Generated pages
All three pages are computed when the site is built (
utils.jl), so nobody has to keep them up to date by hand./toolchains/comes from BinaryBuilderBase:supported_platforms(), showing which GCC, Rust and OCaml versions it has. It uses the same rules aschoose_shardswith the default LLVM, so gaps show up: riscv64 has only GCC 14 and 15, Apple silicon only 12.0.1-iains and 15.2.0, and x86_64 FreeBSD only 6.1 and later./gpus/covers NVIDIA, AMD, Intel, Apple and the cross-vendor OpenCL, Vulkan and SPIR-V:platforms/cuda.jl./mpi/: the 5 MPI implementations, which versions each is compatible with, their latest registered versions, which platforms each is built for, and how users switch between them with MPIPreferences. This comes from Yggdrasil'splatforms/mpi.jl.The homepage's platform count (18), toolchain count (50, which replaces the stale 45), OS list and CPU list come from the same data. The toolchain count is the number of distinct compiler versions: 13 GCC, 17 LLVM, 13 Rust, 6 Go and 1 OCaml.
To answer the question in the issue: the toolchain count isn't
platforms × (gcc + llvm). Each LLVM version is a single build that targets every platform, and GCC versions don't cover every platform.Homepage
rows="27attribute on the asciinema player was never closed, so the browser dropped thepostersetting and the demo started on a blank frame.alttext.Build
Project.tomllists Franklin, NodeJS, BinaryBuilderBase, Downloads and RegistryInstances, with compat bounds. A BinaryBuilderBase 2.0 release can't break the build unannounced.master, on pull requests, weekly (so generated pages pick up upstream changes) and on demand.masteronly.actions/checkoutandjulia-actions/setup-juliaare updated to their current majors.platforms/cuda.jlandplatforms/mpi.jlfrom Yggdrasil'smasterand runs them against BinaryBuilderBase, which avoids installing all of BinaryBuilder.YGGDRASIL_DIRto use one.Project.toml,Manifest.tomland the npm files CI creates are kept out of__site..gitlab-ci.ymland Franklin template assets are removed.Testing
🤖 Generated with Claude Code