Searched refs:analysis (Results 1 – 14 of 14) sorted by relevance
| /build/make/tools/ide_query/ide_query_proto/ |
| D | ide_query.proto | 21 // Indicates the success/failure for analysis.
89 // proto files etc. that were used during analysis. Used to figure
95 // Represents analysis status for this particular file. e.g. not part
108 // Status representing overall analysis.
109 // Should fail only when no analysis can be performed.
|
| /build/make/tools/ |
| D | mk2bp_catalog.py | 172 for analysis in makefile.analyses.values():
173 if analysis:
762 for analyzer, analysis in makefile.analyses.items():
763 if analysis:
917 for analysis in entry:
919 "filename": analysis.filename,
922 [m for m in self.soong.reverse_makefiles[analysis.filename] if m in mods]),
925 for lineno, text in analysis.line_matches]),
1001 def make_annotation_link(self, analysis, modules): argument
1002 if analysis:
[all …]
|
| /build/bazel/rules/android/android_binary_aosp_internal/test/ |
| D | test.bzl | 23 …"""Basic analysis test that checks android_binary_aosp_internal returns AndroidBinaryNativeLibsInf…
28 ctx: The analysis test context
31 The analysis test result
|
| /build/bazel/rules/apex/ |
| D | README.md | 21 * `apex_test.bzl` for Starlark analysis tests
62 * Comprehensive set of rule analysis tests for in `apex_test.bzl`
66 **Known issues / gap analysis (non-exhaustive)**
|
| D | apex_test.bzl | 149 # unfortunately, due to bazel analysis not being able to read the
1886 # An empty analysis test that just ensures the target_under_test can be analyzed.
|
| /build/soong/ui/metrics/bazel_metrics_proto/ |
| D | bazel_metrics.proto | 28 // E.g. "execution", "analysis", "launch"
|
| /build/bazel/scripts/difftool/ |
| D | README.md | 31 5. Run comparative analysis on the two tmp directories. (See
|
| /build/bazel/docs/ |
| D | internal_concepts.md | 30 Blueprint's [Generate and Write phases](#blueprint-analysis) | Analysis Phase …
55 Some other common phony goals include: `nothing` (perform loading/analysis),
74 are resolved during [blueprint analysis](#blueprint-analysis) via the various
239 ### Blueprint Generate & Write phase {#blueprint-analysis}
466 configuration at analysis phase. However, within a macro (at loading phase,
467 before analysis phase), a `select()` is an opaque type that cannot be inspected.
601 …af712d1d241f01fef16649562ba/src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java#…
|
| D | concepts.md | 18 …dable units in `Android.mk`. Generates Ninja file directly.|Loading and analysis phase. Conceptual…
20 … Generates a `.mk` file with prebuilt module stubs to Kati.|Loading and analysis phase. Conceptual…
25 …nger in use. Entire build system, replaced by the tools above.|Loading, analysis, execution phases…
|
| /build/bazel/toolchains/clang/host/linux-x86/ |
| D | cc_toolchain_clang_version_test.bzl | 190 fails in analysis due to missing files from these filegroups.
|
| /build/soong/ui/metrics/metrics_proto/ |
| D | metrics.proto | 136 // which were responsible for retriggering build analysis.
137 // Note that not all changed environment variables result in analysis retriggering.
|
| /build/bazel_common_rules/dist/ |
| D | dist.bzl | 140 for Bazel analysis to succeed due to the nature of testonly enforcement
|
| /build/soong/docs/ |
| D | tidy.md | 4 coding style, error-prone/performance patterns, and static flow analysis.
|
| /build/make/tools/releasetools/ |
| D | pylintrc | 122 # and thus existing member attributes cannot be deduced by static analysis
|