Commits on Source (7)
-
Matthew Clarkson authored
Implements a nice label in the release page for the source archive.
-
Matthew Clarkson authored
Allows setting up resolved toolchains for multi-call binaries.
-
Matthew Clarkson authored
This allows the implicit `:resolved` target to be used even when the local binary is not provided. Technically, we can avoid that because one could set up both `local` _and_ `resolved` repository rules. That is a boilerplate pain though. This moves the error to execution time which is a bit of a pain. Previously, because the repository was only resolved when a target explicitly requested the local toolchain the error would be caught before execution time. However, moving the convenience `:resolved` target into the `local` repository nullifies that because the repository needs to be resolved for _any_ toolchain because the `:resolved` target is re-used. The trade-off here seems worth it for simple `MODULE.bazel` repository definitions.
-
Matthew Clarkson authored
-
Matthew Clarkson authored
-
Matthew Clarkson authored
-
Bot authored
# [1.0.0-alpha.2](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.1...v1.0.0-alpha.2) (2023-11-16) ### Bug Fixes * **resolved:** forward on `basename` attribute ([e71e807b](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/e71e807b6ded13a3baf2d430900f675a1f8849fd)) * **test:** correctly output `stderr` from toolchain executable on error ([22cd1081](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/22cd108126e8917d7142d7f447fdc61f69ea2521)) ### Features * **local_which:** make local binaries non-mandatory ([5d9a292c](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/5d9a292cfd4a7f9dd5b952ca33c34b01da0fc796))