Lines Matching full:abi

48 ABI=
64     --abi=*) ABI=$optarg;;
128     its primary CPU ABI, and build the test program for it. You can however
129     use the --abi=<name> option to override this (this can be useful to check
130     the secondary ABI, e.g. using --abi=armeabi to check that such a program
134     not run) with the default '$DEFAULT_ABI' ABI. Again, you can use
135     --abi=<name> to override this. Valid ABI names are:
154       --abi=<name>     Specify target CPU ABI [auto-detected].
266 # Extract CPU ABI and architecture from device, if any.
268   DEVICE_ABI=$(adb_shell getprop ro.product.cpu.abi)
271     panic "Can't extract ABI from connected device!"
276     dump "Found device ABI: $DEVICE_ABI"
280   # If --abi=<name> is used, check that the device supports it.
281   if [ "$ABI" -a "$DEVICE_ABI" != "$ABI" -a "$DEVICE_ABI2" != "$ABI" ]; then
282     dump  "ERROR: Device ABI(s) do not match --abi command-line value ($ABI)!"
286   if [ -z "$ABI" ]; then
287     ABI=$DEVICE_ABI
288     dump "Using CPU ABI: $ABI (device)"
290     dump "Using CPU ABI: $ABI (command-line)"
293   if [ -z "$ABI" ]; then
294     # No device connected, choose default ABI
295     ABI=$DEFAULT_ABI
296     dump "Using CPU ABI: $ABI (default)"
298     dump "Using CPU ABI: $ABI (command-line)"
302 # Check the ABI value
305   if [ "$ABI" = "$VALID_ABI" ]; then
312   panic "Unknown CPU ABI '$ABI'. Valid values are: $VALID_ABIS"
315 # Extract architecture name from ABI
316 case $ABI in
318   *) ARCH=$ABI;;
418 run "$NDK_DIR/ndk-build" -C "$PROJECT_DIR" $NDK_BUILD_FLAGS APP_ABI=$ABI
430 TESTAPP_FILE="$PROJECT_DIR/libs/$ABI/test_google_breakpad"
432   panic "Device requires '$ABI' binaries. None found!"
465                 $PROJECT_DIR/obj/local/$ABI/$TESTAPP >$TESTAPP.sym"
467 "$TMPBIN/dump_syms" "$PROJECT_DIR/obj/local/$ABI/$TESTAPP" > $TESTAPP.sym