| commit | cbea60144f185848bd9342820471a436058deaf6 | [log] [tgz] |
|---|---|---|
| author | Googler <shahan@google.com> | Mon Dec 05 20:34:32 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 05 20:35:47 2022 -0800 |
| tree | 939382c3a3917d93d1ccbdb5c4f6813ca12ceb0b | |
| parent | 28d2daae70be6ee97b876b0568796ceb87af9523 [diff] |
Remove CTaD from ConfiguredAspectFactory and CTFactory.createAspect. The motivation is to cut CTFunction's dependency on Targets of its dependencies. The plan to achieve this uses ConfiguredTargetAndData (CTaD) as an abstraction layer. CTaD will no longer directly expose the underlying target and instead hide information behind API calls. ConfiguredAspectFactory previously depended on CTaD for direct access to the Target. There are Target fields used for aspect creation that are not needed more broadly. So instead of depending on CTaD, this change makes ConfiguredAspectFactory depend on the broken down ConfiguredTarget and Target components. PiperOrigin-RevId: 493189240 Change-Id: Ie255321a2383d9ee06cb64121fce7799d4b65cce
{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
