armandomontanez
armandomontanez
The [current instructions for installing Bazelisk](https://github.com/bazelbuild/bazelisk/tree/24935f4ce663d6eb79e428005b763c059b508866?tab=readme-ov-file#installation) are not user-friendly. Generally, the widely expected ways to get a tool on the following platforms are: - Windows: Download an `.exe` installer that...
### Description of the bug: Due to limitations with `config_setting` rules used in `target_compatible_with` (also see https://github.com/bazelbuild/bazel/issues/12614), I use a lot of `select`-based `target_compatible_with` expressions. Unfortunately, this usually means the...
Adds a Bazel build for Picotool. The Bazel build comes with a few perks: 1. You don't need to set `PICO_SDK_PATH`. It's still possible to locally override with `--override_module=pico-sdk=/path/to/pico-sdk`. 2....
When creating a rule-based toolchain, legacy features must be explicitly enabled in order for tool invocations to be correctly constructed. This can be done in one of two ways: 1....
Maybe I'm missing something here, but it seems there's no practical way to just cleanly package a `cc_binary` that requires shared libraries or other runfiles. This is the most obvious...
While building out a set of rules, I've been mentioning various rules and rule attributes in doc strings, and wasn't able to find any portable way to do cross referencing...
Updates rules_cc to v0.0.10 to reduce the steps required to get started with creating a Bazel-based Pi Pico project.
Fixes the Windows MSVC Bazel build for Picotool.
Makes the PICOTOOL_VERSION define use the value of module_version() to reduce duplication of version strings in the Bazel build.
When the same tool is listed twice for different actions in a `cc_tool_map`, an error occurs: ``` # ERROR: /private/var/tmp/_bazel_amontanez/e724b21efc8bc19866072fbc72ee5907/external/_main~_repo_rules~llvm_toolchain/BUILD:60:12: Label '@@_main~_repo_rules~llvm_toolchain//:clang' is duplicated in the 'tools' attribute of rule...