Skip to content

feat(stack): buildenv names the toolchains of a build list without a build environment - #58

Merged
HaoZeke merged 3 commits into
mainfrom
feat/stack-buildenv
Nov 19, 2026
Merged

HaoZeke merged 3 commits into
mainfrom
feat/stack-buildenv

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator
eb-stack stack buildenv --build-list site.list --installed modules.txt
GCC-15.2.0      11 lines  listed     buildenv-default-GCC-15.2.0.eb
NVHPC-26.9       5 lines  missing    add buildenv-default-NVHPC-26.9.eb
foss-2026.1     30 lines  installed  buildenv/default-foss-2026.1
...
4 of 9 toolchains have no buildenv module
  • Every toolchain a line builds with is installed (an --installed listing has buildenv/default-<toolchain>), listed (a line of the lists builds it) or missing, with the easyconfig to add.
  • System recipes, comments and the buildenv lines themselves are not counted as users of a toolchain.
  • --json gives the rows with the list and line where each toolchain is first used.
  • Exit status 0; --strict exits 1 while a toolchain has no build environment.
  • MCP: eb_stack_buildenv (the catalog has 65 tools).

Docs: reference/cli, reference/mcp, the README tool list, and the regenerated llms-full.txt.

Checked

Unit tests in src/buildenv.rs; cargo fmt --all --check and cargo clippy --locked --all-targets -- -D warnings pass with Rust 1.94.1.

Closes #57

…build environment

stack buildenv reads build lists and an installed-module listing and
reports, per toolchain a line builds with, whether its
buildenv/default-<toolchain> module is installed, listed or missing,
with the easyconfig that adds it. --strict exits 1 while one is
missing. The MCP catalog gains eb_stack_buildenv.
@HaoZeke
HaoZeke merged commit c98bed7 into main Nov 19, 2026
22 checks passed
@HaoZeke
HaoZeke deleted the feat/stack-buildenv branch November 19, 2026 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

stack: nothing says which toolchains of a build list lack a buildenv module

1 participant