Allow platforms with slashes in their names in output paths (#31600) ### Description With `--experimental_use_platforms_in_output_dir_legacy_heuristic` (the default), the name of the target platform becomes the first component of the output directory mnemonic. Slashes in that name are now replaced with underscores, so `platform(name = "foo/bar")` results in `bazel-out/foo_bar-fastbuild` instead of failing analysis. This can make two platforms share an output directory, but that is already the case for platforms with the same name in different packages. Falling back to the `platform-<hash>` form used without the legacy heuristic would avoid that, but would also make the output directory unreadable for these platforms. ### Motivation Target names may contain slashes, but such platforms failed analysis with `CPU/Platform descriptor 'foo/bar' is invalid as part of a path: must not contain /`. Since `--experimental_platform_in_output_dir` defaults to `auto` in Bazel 9, this affects every exec configuration with such an execution platform. Fixes #31596 ### Build API Changes No ### Release Notes RELNOTES: Platforms whose names contain `/` no longer fail analysis when used in output directory names. Closes #31600 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31600 from fmeum:platform-name-with-slash 1b9488416872279f7eb403cef61acc3adf986120 PiperOrigin-RevId: 996792452 Change-Id: I3eac1a916aade404eefdec50336c5a7a930a9684
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
