Searched refs:variables (Results 1 – 25 of 38) sorted by relevance
12
/system/apex/ |
D | Android.bp | 23 variables: ["library_linking_strategy"], 36 variables: ["library_linking_strategy"],
|
D | pylintrc | 174 # note). You have access to the variables errors warning, statement which 328 # A regular expression matching the name of dummy variables (i.e. expectedly 330 dummy-variables-rgx=^\*{0,2}(_$|unused_|dummy_)
|
/system/tools/aidl/build/ |
D | aidl_test.go | 48 return android.FixtureModifyProductVariables(func(variables android.FixtureProductVariables) { 50 variables.Platform_sdk_version = intPtr(29) 51 variables.Platform_sdk_codename = proptools.StringPtr("REL") 52 variables.Platform_sdk_final = proptools.BoolPtr(true) 53 variables.Platform_version_active_codenames = []string{} 141 …preparers = append(preparers, android.FixtureModifyProductVariables(func(variables android.Fixture… 144 variables.Platform_sdk_version = intPtr(28) 145 variables.Platform_sdk_codename = proptools.StringPtr("Q") 146 variables.Platform_version_active_codenames = []string{"Q"} 147 variables.Platform_sdk_final = proptools.BoolPtr(false)
|
/system/update_engine/update_manager/ |
D | evaluation_context.cc | 232 auto variables = std::make_unique<base::DictionaryValue>(); in DumpContext() local 234 variables->SetString(it.first->GetName(), it.second.ToString()); in DumpContext() 238 value.Set("variables", std::move(variables)); in DumpContext()
|
/system/chre/doc/ |
D | framework_build.md | 10 variables. While the CHRE framework source code may be integrated into another 33 All variant-specific compiler and linker flags are held under variables that 51 with all the variables used to generate build targets, like `TARGET_CFLAGS`. 90 CHRE expects the build toolchain to be exported via Makefile variables, 134 variables prefixed with the platform name (for example, `SIM_SRCS` for platform 136 common variables, to avoid affecting other build targets.
|
/system/extras/simpleperf/demo/SimpleperfExampleWithNative/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 78 @rem End local scope for the variables with windows NT shell
|
/system/extras/power_profile/camera_avg/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 78 @rem End local scope for the variables with windows NT shell
|
/system/extras/simpleperf/demo/SimpleperfExamplePureJava/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 78 @rem End local scope for the variables with windows NT shell
|
/system/extras/simpleperf/demo/SimpleperfExampleOfKotlin/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 78 @rem End local scope for the variables with windows NT shell
|
/system/extras/power_profile/gps_on/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 78 @rem End local scope for the variables with windows NT shell
|
/system/extras/simpleperf/demo/CppApi/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 72 @rem End local scope for the variables with windows NT shell
|
/system/extras/power_profile/camera_flashlight/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 78 @rem End local scope for the variables with windows NT shell
|
/system/extras/simpleperf/demo/JavaApi/ |
D | gradlew.bat | 8 @rem Set local scope for the variables with windows NT shell 72 @rem End local scope for the variables with windows NT shell
|
/system/netd/ |
D | Android.bp | 74 "-misc-non-private-member-variables-in-classes", // Also complains about structs
|
/system/core/fs_mgr/libsnapshot/ |
D | PowerTest.md | 38 Two environment variables can be passed to `run_power_test.sh`:
|
/system/sepolicy/ |
D | README | 46 variables have been deprecated in favour of SYSTEM_EXT_*. 98 and tags start with @. The option arguments can also use environment variables
|
/system/bt/service/ |
D | Android.bp | 23 // Source variables
|
/system/chre/chpp/ |
D | QUICKSTART.md | 14 1. Condition variables
|
/system/bt/doc/ |
D | style_guide.md | 64 * use `static const` variables instead of `#define` 96 In nearly all cases, variables should be declared and initialized on the same line. 109 As a result of the above rule to declare and initialize variables together,
|
/system/tools/aidl/ |
D | generate_java.cpp | 442 std::vector<std::string> variables; in generate_parcel_class() local 444 std::back_inserter(variables), [](const auto& f) { return f->GetName(); }); in generate_parcel_class() 445 out << base::Join(variables, ", ") << ");\n" in generate_parcel_class()
|
/system/tools/mkbootimg/ |
D | pylintrc | 168 # note). You have access to the variables errors warning, statement which 321 # A regular expression matching the name of dummy variables (i.e. expectedly 323 dummy-variables-rgx=^\*{0,2}(_$|unused_|dummy_)
|
/system/update_engine/ |
D | pylintrc | 116 # note). You have access to the variables errors warning, statement which 198 # A regular expression matching names used for dummy variables (i.e. not used). 199 dummy-variables-rgx=^\*{0,2}(_$|unused_|dummy_)
|
/system/core/fastboot/ |
D | Android.bp | 160 "device/variables.cpp",
|
D | README.md | 120 variables, so older devices might exhibit this behavior, 162 The "getvar:%s" command is used to read client variables which 252 In this example the fastboot host queries the device for two variables,
|
/system/bt/btif/ |
D | Android.bp | 1 // Common variables
|
12