Searched refs:used (Results 1 – 25 of 66) sorted by relevance
123
/build/soong/docs/ |
D | map_files.md | 49 These map files can (and should) also be used as version scripts for building 68 interpreted by the stub generator. Multiple space-delimited tags may be used on 74 than the NDK. May be used in combination with `llndk` if the symbol is exposed 80 level. This is an arbitrarily high API level used to define APIs that have not 84 but **will not be included in the NDK**. `future` should generally not be used, 103 Code names can (and typically should) be used when defining new APIs. This 105 that release. For example, `introduced=S` can be used to define APIs added in S. 106 Any code name known to the build system can be used. For a list of versions 122 Note: The architecture-specific tags should, in general, not be used. These are 130 than the NDK. May be used in combination with `apex` if the symbol is exposed to [all …]
|
D | best_practices.md | 101 will be used as a list of sources is useful, both for humans and automated 102 tools. This is even more useful if it's used inside an architecture or 145 they're used dynamically via `dlopen`. If they're only used via 241 used to partition a set of modules so that they are built only when the 276 ### Conditionally used source files, libraries or flags 286 plugins should be used only when absolutely required.
|
/build/soong/cmd/extract_apks/bundle_proto/ |
D | config.proto | 33 // Version of BundleTool used to build the Bundle. 74 // Optimization configuration used to generate Split APKs. 79 // Optimization configuration used to generate Standalone APKs. 119 // The default suffix to be used for the cases where separate slices can't 127 // used (for example, if both "assets/level1_textures#tcf_etc1" and 129 // then only "assets/level1_textures" will be used).
|
/build/make/target/product/security/ |
D | README | 5 The test keys in this directory are used in development only and should 6 NEVER be used to sign packages in publicly released images (as that would 12 The following commands were used to generate the test key pairs:
|
/build/make/target/board/generic_64bitonly_x86_64/ |
D | README.txt | 4 It can be used to build the entire user-level system, and
|
/build/make/target/board/generic_x86/ |
D | README.txt | 4 It can be used to build the entire user-level system, and
|
/build/make/target/board/generic/ |
D | README.txt | 4 It can be used to build the entire user-level system, and
|
/build/make/core/ |
D | soong_android_app_set.mk | 6 $(call pretty-error,soong_apk_set.mk may only be used from Soong)
|
D | local_vndk.mk | 37 …$(shell echo $(LOCAL_MODULE_MAKEFILE): $(LOCAL_MODULE): LOCAL_USE_VNDK must not be used with LOCAL…
|
D | distdir.mk | 55 $(KATI_obsolete_var dist-for-goals,Cannot be used after dist-write-file) \
|
D | copy_headers.mk | 7 $(call pretty-error,LOCAL_COPY_HEADERS may not be used with host modules)
|
D | soong_droiddoc_prebuilt.mk | 4 $(call pretty-error,soong_droiddoc_prebuilt.mk may only be used from Soong)
|
D | build_id.rbc | 19 …# BUILD_ID is usually used to specify the branch name (like "MAIN") or a branch name and a release…
|
D | dumpconfig.mk | 9 $(warning Kati must be used to call dumpconfig.mk, not make.)
|
/build/make/target/board/generic_x86_arm/ |
D | README.txt | 4 It can be used to build the entire user-level system, and
|
/build/make/target/board/generic_x86_64_arm64/ |
D | README.txt | 4 It can be used to build the entire user-level system, and
|
/build/bazel/platforms/os/ |
D | BUILD | 1 # Standard constraint_setting and constraint_values to be used in platforms.
|
/build/make/tools/releasetools/ |
D | pylintrc | 38 # be used to obtain the result of joining multiple strings with the addition 86 # number of statements analyzed. This is used by the global evaluation report 90 # Add a comment according to your evaluation note. This is used by the global 94 # Template used to display messages. This is a python new-style format string 95 # used to format the message information. See doc for all details 147 # List of builtins function names that should not be used, separated by a comma 267 # String used as indentation unit. This is usually " " (4 spaces) or "\t" (1 291 # not used). 339 # Deprecated modules which should not be used, separated by a comma 357 # List of method names used to declare (i.e. assign) instance attributes.
|
/build/make/tools/fs_config/ |
D | README.md | 15 results. The Target files are used by filesystem and adb tools to ensure that the file and directory 16 properties are preserved during runtime operations. The host files in the `$OUT` directory are used 24 used by bionic for implementing `getpwnam()` and related functions.
|
/build/soong/scripts/ |
D | check_do_not_merge.sh | 20 and are not allowed to be used in this project.
|
/build/blueprint/proptools/ |
D | unpack.go | 42 used bool member 93 if v.used { 268 packedProperty.used = true 369 packedProperty.used = true
|
/build/make/tools/signapk/ |
D | Android.bp | 17 // the signapk tool (a .jar application used to sign packages)
|
/build/soong/android/ |
D | singleton_module_test.go | 82 `\QDuplicate SingletonModule "test_singleton_module", previously used in\E`,
|
/build/soong/cmd/pom2mk/ |
D | pom2mk.go | 358 rewrite can be used to specify mappings between Maven projects and Make modules. The -rewrite 361 either the Maven project's <groupId>:<artifactId> or <artifactId> will be used to generate 362 the Make module name using <replace>. If no matches are found, <artifactId> is used. 373 -use-version can be used to only write makefiles for a specific version of those artifacts.
|
/build/make/tools/ |
D | brillo-clang-format | 20 # This is the .clang-format file used by all Brillo projects, conforming to the
|
123