Commits on Source (3)
-
Matthew Clarkson authored
Splitting out `resolved`/`which` repository rules makes sense. It prevents any missing tools from raising an error in the toolchain resolution rather than later via the stub. This is _much_ more **user** friendly. Including the `resolved` target in the local repository was more **developer** friendly as it negated the need for two repositories. We want to be **user** friendly.
-
Matthew Clarkson authored
-
Bot authored
# [1.0.0-alpha.10](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.9...v1.0.0-alpha.10) (2023-12-13) ### Features * make `which` mandatory ([274d2c96](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/274d2c96991ea897a76055527561e5346402792a))
Showing
- CHANGELOG.md 6 additions, 0 deletionsCHANGELOG.md
- MODULE.bazel 1 addition, 1 deletionMODULE.bazel
- README.md 8 additions, 3 deletionsREADME.md
- e2e/MODULE.bazel 2 additions, 3 deletionse2e/MODULE.bazel
- e2e/MODULE.bazel.lock 19 additions, 21 deletionse2e/MODULE.bazel.lock
- e2e/toolchain/echo/BUILD.bazel 3 additions, 3 deletionse2e/toolchain/echo/BUILD.bazel
- toolchain/local/which/BUILD.tmpl.bazel 2 additions, 8 deletionstoolchain/local/which/BUILD.tmpl.bazel
- toolchain/local/which/repository.bzl 10 additions, 35 deletionstoolchain/local/which/repository.bzl
- toolchain/local/which/stub.bat 0 additions, 28 deletionstoolchain/local/which/stub.bat
- toolchain/local/which/stub.sh 0 additions, 16 deletionstoolchain/local/which/stub.sh
- toolchain/resolved/BUILD.tmpl.bazel 1 addition, 1 deletiontoolchain/resolved/BUILD.tmpl.bazel
- toolchain/resolved/repository.bzl 4 additions, 0 deletionstoolchain/resolved/repository.bzl
toolchain/local/which/stub.bat
deleted
100644 → 0
toolchain/local/which/stub.sh
deleted
100755 → 0