Searched refs:used (Results 1 – 25 of 53) 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 67 interpreted by the stub generator. Multiple space-delimited tags may be used on 73 than the NDK. May be used in combination with `llndk` if the symbol is exposed 79 level. This is an abitrarily high API level used to define APIs that have not 96 Codenames can (and typically should) be used when defining new APIs. This allows 98 release. For example, `introduced=S` can be used to define APIs added in S. Any 99 code name known to the build system can be used. For a list of versions known to 115 Note: The architecture-specific tags should, in general, not be used. These are 123 than the NDK. May be used in combination with `apex` if the symbol is exposed to 142 tag may be used. [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/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/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_x86_64/ |
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/target/board/generic_x86_64_arm64/ |
D | README.txt | 4 It can be used to build the entire user-level system, and
|
/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/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 | 36 …$(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 | notice_files.mk | 25 $(call pretty-error,LOCAL_NO_NOTICE_FILE should not be used by Android.mk files)
|
/build/make/tools/fs_config/ |
D | README | 12 Target files are used by filesystem and adb tools to ensure that the file and directory properties 13 are preserved during runtime operations. The host files in the ${OUT} directory are used in the 18 The passwd and group files are formatted as documented in man pages passwd(5) and group(5) and used 50 prefixed with a 0, else mode is used as is.
|
/build/blueprint/proptools/ |
D | unpack.go | 42 used bool member 93 if v.used { 268 packedProperty.used = true 358 packedProperty.used = true
|
/build/make/tools/signapk/ |
D | Android.bp | 17 // the signapk tool (a .jar application used to sign packages)
|
/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/ |
D | Changes.md | 106 a long time, and the places where it's been able to be used have shrinked over 229 `PRODUCT_PACKAGES` to make installation decisions, but verifies that if we used 242 In Android.mk files, you used to be able to change LOCAL_ARM_MODE for each 246 Soong does not support this uncommonly used behavior, instead expecting those 282 `BUILD_NUMBER` should not be used directly in Android.mk files, as it would 329 `.PHONY`-marked targets are often used as shortcuts to provide "friendly" names 401 used. 410 If used during Android.mk files, and later tasks, it is increasingly likely 411 that they are being used incorrectly. Attempting to change the environment for 524 Many other characters already caused problems if you used them, so we don't [all …]
|
D | README.md | 12 but are entirely different from the Android.mk files used by the NDK build
|
/build/make/tools/ |
D | brillo-clang-format | 20 # This is the .clang-format file used by all Brillo projects, conforming to the
|
/build/soong/cmd/pom2bp/ |
D | pom2bp.go | 584 …rewrite can be used to specify mappings between Maven projects and Android.bp modules. The -rewrite 587 either the Maven project's <groupId>:<artifactId> or <artifactId> will be used to generate 588 the Android.bp module name using <replace>. If no matches are found, <artifactId> is used. 603 … -use-version can be used to only write Android.bp files for a specific version of those artifacts.
|
/build/soong/ |
D | README.md | 59 This is commonly used to reference `filegroup` modules, whose output files 111 A defaults module can be used to repeat the same properties in multiple modules. 283 used by other packages. Modules are always visible to other modules declared 293 creating module. Can only be used at the beginning of a list of visibility 300 module and must be used verbatim. It represents all of the modules in the 313 `//visibility:public` for now. It is an error if it is used in a module. 454 The `acme_cc_defaults` module type can be used anywhere after the definition in 463 It can used like any other module type: 496 `soong_config_module_type` modules will work best when used to wrap defaults
|
123