armandomontanez

[discussion] Decide whether or not to express FPU nuances for `@platforms//cpu:armv*-m*` constraints

6

We may want to avoid expressing FPU extensions in ARM Cortex-M CPU constraints. # Proposal Refrain from extending the set of `@platforms//cpu:armv*-mf` constraints, and annotate the existing constraint with a...

[discussion] Deprecate `//cpu:armv8-m` in favor of `//cpu:armv8-m.main`

3

Similar to #100, I'm looking to tidy up some pre-existing Cortex-M CPU expressions here. # Proposal Mark `//cpu:armv8-m` as deprecated, and introduce `//cpu:armv8-m.base` and `//cpu:armv8-m.main`. # Why? ARMv8-M is technically...

Large integers in version strings can cause some older Bazel releases to crash with a NumberFormatException.

C++ host compile actions can conflict when --experimental_platform_in_output_dir is enabled

1

### Description of the bug: When `--experimental_platform_in_output_dir` is enabled, any C++ compile actions targeting `@local_config_platform//:host` will conflict with identical actions targeting `@platforms//host`. ### Which category does this issue belong to?...

`evaluate_markers_py()` does not work with `bazel vendor`

2

# 🐞 bug report ### Affected Rule `//python/private/pypi:evaluate_markers.bzl` --> `evaluate_markers_py` ### Is this a regression? No (AFAIK), this likely never worked. ### Description Because of how runfiles are managed, `evaluate_markers_py()`...

Fixes `bazel vendor` support for requirements files that contain environment markers. During a vendored `bazel build`, when evaluate_markers_py() is run it needs PYTHONHOME set to properly find the home of...

Adds Bazel build integration for quite a few Pico W examples.

Initial libtool support

3

Introduces initial support for linking static archives via macOS's libtool to support cases where AR is explicitly set to libtool or llvm-libtool-darwin.