Paul Janzen

Results 16 comments of Paul Janzen

Let targets set their flags / platforms without command-line flags

isn't this provided by [platform_mappings](https://docs.bazel.build/versions/main/platforms-intro.html#platform-mappings)?

Using `--cpu=darwin_x86_64` in `platform_mappings` triggers unnecessary toolchain evaluation

The use case being discussed here is: - A multi-platform repository, containing some apple targets (e.g., objc_library), and - A platform_mappings file that is used to cause platform-specific constraints to...

Using `--cpu=darwin_x86_64` in `platform_mappings` triggers unnecessary toolchain evaluation

At the risk of stating the obvious, this is a problem inherent to _any_ rule that self-transitions on `--platform` or `--cpu`, not just `objc_library`.

v 5 cc_library, linkstatic=False fails to emit .so file

The default mac toolchain stopped supporting dynamic linking in 5.0: ec5553352

incompatible_build_transitive_python_runfiles

Will #14740 be merged as a prerequisite for this change? If not, won't it wildy exacerbate the problem in #11997?

Inherit exec_group setting from build actions when selecting executable

related: https://github.com/bazelbuild/bazel/issues/11432 and https://github.com/bazelbuild/bazel/issues/19904

Cannot pass envvar to app launched by bazel run without invalidating repo and triggering rebuild

You mentioned Windows, so this may not work for you, but on Unix-y platforms you can pass environment variables to `bazel run` while preventing them from being seen by repo...

data files aren't copied / symlinked from the execroot to the sandbox

This looks like a protobuf issue to me. When a target appears in the `tools` attribute of a genrule, its data files are only placed in the execroot if the...

Scheduling tests that require exclusive access to limited resources

previously: https://github.com/bazelbuild/bazel/issues/12467

Absolute path inclusion validation breaks C++26's `#embed` on Clang / macOS

Note that if you do provide `--embed-dir` with a relative path, and the resource is found via that path, then (at least my version of) clang will write a relative...