Searched refs:custom (Results 1 – 25 of 60) sorted by relevance
123
24 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_bad33 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_static42 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_v1
36 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_v148 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_v261 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_v172 LOCAL_AAPT_FLAGS := --custom-package $(my_package_prefix)_v2
12 # Internal utility function: Create a custom target representing a build of examples with custom op…
8 "--custom-package com.google.android.dexapis.splitapp.feature_a",
4 ADR;X-custom:pobox;street
423 final View custom = tab.getCustomView(); in update() local424 if (custom != null) { in update()425 final ViewParent customParent = custom.getParent(); in update()427 if (customParent != null) ((ViewGroup) customParent).removeView(custom); in update()428 addView(custom); in update()430 mCustomView = custom; in update()
35 // A proto file used to test the "custom options" feature of google.protobuf.45 // A custom file option (defined below).55 // Some simple test custom options of various types.97 // A test message with custom options at all possible locations (and also some121 // A test RPC service with custom options at all possible locations (and also390 // Test custom options for nested type.414 // Updated version of the custom option above.
103 // If the embedded message type is well-known and has a custom JSON105 // `value` which holds the custom JSON in addition to the `@type`
259 // Clients may define custom options as extensions of the *Options messages.267 // Extension numbers for custom options may be chosen as follows:385 // Clients can define custom options in extensions of this message. See above.449 // Clients can define custom options in extensions of this message. See above.539 // Clients can define custom options in extensions of this message. See above.547 // Clients can define custom options in extensions of this message. See above.566 // Clients can define custom options in extensions of this message. See above.580 // Clients can define custom options in extensions of this message. See above.600 // Clients can define custom options in extensions of this message. See above.620 // Clients can define custom options in extensions of this message. See above.
35 // A proto file used to test the "custom options" feature of proto2.44 // A custom file option (defined below).54 // Some simple test custom options of various types.92 // A test message with custom options at all possible locations (and also some111 // A test RPC service with custom options at all possible locations (and also374 // Test custom options for nested type.
215 // Clients may define custom options as extensions of the *Options messages.223 // Extension numbers for custom options may be chosen as follows:303 // Clients can define custom options in extensions of this message. See above.336 // Clients can define custom options in extensions of this message. See above.418 // Clients can define custom options in extensions of this message. See above.431 // Clients can define custom options in extensions of this message. See above.439 // Clients can define custom options in extensions of this message. See above.453 // Clients can define custom options in extensions of this message. See above.467 // Clients can define custom options in extensions of this message. See above.
6 # We need the built .class files to load custom views and R class.
6 A driver can provide custom hardware-accelerated operations via NNAPI 1.2+49 * A custom scalar type.54 * A custom tensor type.80 Extensions may also declare custom structures to accompany extension operands:
1 Layoutlib is a custom version of the android View framework designed to run inside Eclipse.
42 // Use a custom AndroidManifest.xml used for API targeting.77 // Use a custom AndroidManifest.xml used for API targeting.
26 "--custom-package",
25 "--custom-package",
2 In order to build using prebuild NDK versions, this project must be initialized from a custom repo …
12 want to test against what we wrote in the tree. Because of this we use a custom test runner,
10 on some custom dependency injection provided by Dependency.77 Provides custom dependency injection.146 Component allowing the vendor/OEM to inject a custom component.
12 # GAMESDK_DO_BUILD: whether to add a custom build command to build the gamesdk (ON/OFF)
269 // Note: Now that there isn't a custom string class under the hood, this test270 // isn't as critical, but it does cover bad input and if a custom class is added300 // correctly. (Again, this is inpart incase a custom string class is ever
11 // Generate custom headers