[9.0.2] Fix launcher/launcher_maker for cross build (https://github.com/bazelbuild/bazel/pull/29200) (#29238) ### Description Fix launcher/launcher_maker for cross build. launcher will be used in the build output, so it should use cfg=target. launcher_maker is used to combine a binary for target and launcher for target into the final output at build time, so it should use cfg=exec. ### Motivation To make py_binary launcher work when building on linux (exec) for windows (target). ### Build API Changes No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes RELNOTES: Fix launcher/launcher_maker for cross build, e.g. build windows binary on linux machine. Closes #29200. PiperOrigin-RevId: 895761405 Change-Id: I0b3dd3431d25fb4fb9ea827f344eb5cf42c11276 Commit https://github.com/bazelbuild/bazel/commit/4ff312727ec3eedb4f1206127393819917ec2714 Co-authored-by: Boleyn Su <boleyn.su@gmail.com>
{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.
Follow our tutorials:
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
