| commit | 9b4844a0ca3ee031c8b930c23d551da6a9050a85 | [log] [tgz] |
|---|---|---|
| author | John Laxson <jlaxson@mac.com> | Tue Oct 19 08:05:47 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 19 08:06:57 2021 -0700 |
| tree | 7b2a15c333f9952de76b4b28e9d879ac3e2d3737 | |
| parent | 70ee973440116c6057ba00397138e9b0aaaeac56 [diff] |
Allow oso_prefix_is_pwd to be used with all osx cpp link actions Expands the targeted actions to allow stripping the absolute build path for debug symbols from all libraries. The support in wrapped_clang is indifferent to whether we are linking a true objc or regular cpp library. When used in concert with `--features=oso_prefix_is_pwd --remote_download_outputs=all`, allows successful local debugging of executables/libraries built remotely. Probably also helps with sandboxed actions. Helps mitigate #6327 and kinda sorta #2537? See also #11671 Closes #13311. PiperOrigin-RevId: 404262861
{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
