Searched refs:graph (Results 1 – 25 of 28) sorted by relevance
12
/build/bazel/scripts/bp2build-progress/ |
D | README.md | 6 This tool relies on `json-module-graph` and `bp2build` to be buildable targets 12 * Optional: `/usr/bin/jq`: running the query scripts over the json-module-graph. 33 ./bp2build-progress.py graph -m adbd > /tmp/graph.in && dot -Tpng -o /tmp/graph.png /tmp/graph.in 39 ./bp2build-progress.py graph -m adbd --use_queryview=true > /tmp/graph.in && dot -Tpng -o /tmp/grap…
|
/build/make/tools/product_config/ |
D | inherit_tree.py | 11 def PrintNodes(graph, node, prefix): argument 13 children = graph.get(node, []) 16 for child in sorted(graph.get(node, [])): 17 PrintNodes(graph, child, prefix + " ") 28 graph = {} 40 graph.setdefault(line[1], list()).append(line[2]) 42 PrintNodes(graph, root, "")
|
/build/bazel/json_module_graph/ |
D | README.md | 1 # JSON module graph queries 3 This directory contains `jq` scripts that query Soong's module graph. 9 m json-module-graph 10 query.sh [-C] <command> <base-of-your-tree>/out/soong/module-graph.json [argument] 16 in the module graph within the transitive closure of given module 38 It's best to filter the full module graph to the part you are interested in 39 because `jq` isn't too fast on the full graph.
|
/build/soong/tests/ |
D | bootstrap_test.sh | 628 run_soong json-module-graph bp2build nothing 645 run_soong json-module-graph 657 run_soong json-module-graph 658 local json_mtime1=$(stat -c "%y" out/soong/module-graph.json) 666 run_soong json-module-graph 667 local json_mtime2=$(stat -c "%y" out/soong/module-graph.json)
|
/build/make/core/ |
D | ninja_config.mk | 31 product-graph \
|
/build/bazel/examples/soong_config_variables/ |
D | Android.bp | 1 // Use local copy of the soong_config_module_type dep graph to keep this Android.bp
|
/build/make/tools/compliance/cmd/testdata/regressgpl1/ |
D | README.md | 3 ### Testdata build graph structure:
|
/build/make/tools/compliance/cmd/testdata/regressgpl2/ |
D | README.md | 3 ### Testdata build graph structure:
|
/build/make/ |
D | README.md | 20 graph of the two systems can be combined and run as one.
|
/build/make/tools/compliance/cmd/rtrace/ |
D | rtrace.go | 97 resolution in the graph. When -dot flag given, outputs nodes and edges 98 in graphviz directed graph format.
|
/build/make/tools/compliance/cmd/dumpgraph/ |
D | dumpgraph.go | 97 edge in the license graph. When -dot flag given, outputs the nodes and 98 edges in graphViz directed graph format.
|
/build/make/tools/releasetools/ |
D | pylintrc | 342 # Create a graph of every (i.e. internal and external) dependencies in the 344 import-graph= 346 # Create a graph of external dependencies in the given file (report RP0402 must 348 ext-import-graph= 350 # Create a graph of internal dependencies in the given file (report RP0402 must 352 int-import-graph=
|
/build/make/tools/compliance/cmd/dumpresolutions/ |
D | dumpresolutions.go | 98 resolution in the graph. When -dot flag given, outputs nodes and edges 99 in graphviz directed graph format.
|
/build/make/tools/compliance/cmd/testdata/ |
D | README.md | 3 Each non-regression directory under testdata/ defines a similar build graph. 4 All have the same structure, but different versions of the graph have different 10 ### Testdata build graph structure: 123 #### the whole build graph
|
/build/bazel/ci/ |
D | bp2build.sh | 127 …"${bp2build_progress_script}" graph -m "${m}" --use_queryview=true > "${bp2build_progress_output_…
|
/build/soong/compliance/license_metadata_proto/ |
D | license_metadata.proto | 69 // AnnotateDepencency messages describe edges in the build graph.
|
/build/make/tools/compliance/ |
D | Android.bp | 129 "graph.go",
|
/build/soong/docs/ |
D | perf.md | 48 in the build graph will improve total build times. 220 You'll likely need to cross-reference this data against the build graph in the 245 Soong always loads the entire module graph, so as modules convert from Make to 247 does slow down builds, as we need to verify/produce/load a larger build graph.
|
D | best_practices.md | 42 enforce this in the future. Encode these as build rules in the build graph 109 If writing multiple files from a tool, declare them all in the build graph. 135 generate the entire build graph before reading source files, or running your
|
/build/make/tools/canoninja/ |
D | README.md | 141 …we extract only build statements and sort them, we see that both Ninja files define the same graph:
|
/build/soong/dexpreopt/ |
D | DEXPREOPT_IMPLEMENTATION.md | 136 Some build systems, such as Make, allow modifications of the build graph during 140 modifications of the dependency graph during the second phase. The Soong 143 graph modfications continue until fixpoint. However the Soong approach is also
|
/build/bazel/docs/ |
D | concepts.md | 21 |Ninja|Serialized command line action graph executor. Executes Ninja graph generated from Kati and …
|
D | internal_concepts.md | 27 `out/soong/build.ninja` and `out/build-<target>.ninja` | Action graph (serialized) … 273 visitation to every module in the graph.
|
/build/bazel/rules_cc/examples/ |
D | experimental_cc_shared_library.bzl | 26 "Nodes in the graph of shared libraries.",
|
/build/soong/makedeps/ |
D | deps_test.go | 301 external/ninja/src/graph.h external/ninja/src/eval_env.h \
|
12