commit | 9452b8dc38a030a99b4493b51e85e1acd44db93e | [log] [tgz] |
---|---|---|
author | Peter Wen <wnwen@chromium.org> | Tue Apr 19 20:33:57 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 19 20:33:57 2022 |
tree | 39b9f0149543c45828d25666c326d691baa6fa74 | |
parent | b21d16741d78e65297601a354f6bdb361ee9bfd5 [diff] |
Android: Add dep_operations.py Design doc: http://go/gn-deps This CL is a follow-up to https://crrev.com/c/3217679, consolidating split_dep.py as an operation of the new dep_operations.py and adding a new operation to remove dep(s). When removing one or more deps, each time the dep is found, all targets are built. If there are any failures or if no targets are built, the dep is not removed. Otherwise if everything compiles successfully the dep is removed. This is repeated until all build files are processed. Because ninja is used to build all targets, the remove command cannot be run multi-processed like the split command. Usage example: $ tools/android/modularization/gn/dep_operations.py remove \ //build/android:build_java Output is similar to the split command. Typically these two commands are used together to split out deps and then to remove the unnecessary ones so that only the necessary ones are added. Example combination: $ tools/android/modularization/gn/dep_operations.py split \ //base:base_java //build/android:build_java $ tools/android/modularization/gn/dep_operations.py remove \ //build/android:build_java Multiple deps to remove or split is supported to make it easier to work with. For example, if a java_group should be inlined, it can be first split into its deps and then all can be removed (if the targets still build). One caveat is that for the remove command the java_group parent dep should come first so it can always be removed. Bug: 1258168 Change-Id: I20e5f6c4fad0a9b7528c405a376673af1fdf3589 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3521864 Reviewed-by: Henrique Nakashima <hnakashima@chromium.org> Commit-Queue: Peter Wen <wnwen@chromium.org> Auto-Submit: Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/main@{#993877}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.