Lines Matching refs:manifest

7 the target, it shouldn't be in the split manifest. This smaller manifest can be
9 should be faster and smaller than a sync of a full manifest because it is
13 manifest from a full manifest using dependency information from the source tree
21 ### 1. Run a full build using a full manifest
37 # target that should be buildable from your split manifest.
45 # Create the split manifest using a sample config XML specific to aosp_arm64.
47   --manifest .repo/manifests/default.xml \
48   --split-manifest split_default.xml \
54 ### 3. Build using the split manifest
56 You should test that the split manifest created by the tool can be used to build
61 1.  Replace the `.repo/manifests/default.xml` full manifest with the
62     newly-generated split manifest.
73 1.  Find the dependency source project in your full-manifest repo directory.
74 1.  Update your config XML to manually add projects to your split manifest.
78         manifest even if the tool doesn't automatically detect that it is
85 1.  Regenerate the split manifest using `treble_manifest_split` in your
86     full-manifest directory. Remember to pass the path of your config XML to the
92 manifest. You should diff the output artifacts of the split-manifest build
93 against the output artifacts of the full-manifest build.