Home
last modified time | relevance | path

Searched refs:emulator (Results 1 – 25 of 89) sorted by relevance

1234

/external/mdnsresponder/mDNSWindows/DNSServiceBrowser/WindowsCE/
DApplication.vcp6 # TARGTYPE "Win32 (WCE emulator) Application" 0xa601
8 CFG=Application - Win32 (WCE emulator) Debug
17 !MESSAGE NMAKE /f "Application.vcn" CFG="Application - Win32 (WCE emulator) Debug"
21 !MESSAGE "Application - Win32 (WCE emulator) Release" (based on "Win32 (WCE emulator) Application")
22 !MESSAGE "Application - Win32 (WCE emulator) Debug" (based on "Win32 (WCE emulator) Application")
33 !IF "$(CFG)" == "Application - Win32 (WCE emulator) Release"
67 !ELSEIF "$(CFG)" == "Application - Win32 (WCE emulator) Debug"
172 # Name "Application - Win32 (WCE emulator) Release"
173 # Name "Application - Win32 (WCE emulator) Debug"
183 !IF "$(CFG)" == "Application - Win32 (WCE emulator) Release"
[all …]
/external/perfetto/test/ci/
Dandroid_tests.sh22 tools/run_android_emulator --pid /tmp/emulator.pid -v &
34 test -f /tmp/emulator.pid && kill -9 $(cat /tmp/emulator.pid); true
/external/grpc-grpc-java/android-interop-testing/
DREADME.md14 Connect your Android device or start the emulator:
16 $ ./start-emulator.sh <AVD name> & ./wait-for-emulator.sh
41 Instrumentation tests must be run on a connected device or emulator. Run with the
/external/honggfuzz/examples/terminal-emulators/
DREADME.md14 feedback accumulation) will not be closed by the fuzzed binary (terminal emulator)
17 The *terminal-test* program will feed the terminal emulator with data from the
21 ## Step 2: Instrument your terminal emulator ##
23 Add compiler-time instrumentation to your fuzzed terminal emulator. Typically it
87 terminal emulator's input buffer. It will typically contains responses to ESC
93 executed) with whatever runs under said emulator (e.g. _/bin/bash_)
/external/skia/infra/skqp/docker/
DREADME.md9 This image has an Android emulator, the Android SDK and NDK installed on it.
29 # start an emulator
36 # attach to that emulator
/external/skqp/infra/skqp/docker/
DREADME.md9 This image has an Android emulator, the Android SDK and NDK installed on it.
29 # start an emulator
36 # attach to that emulator
/external/webrtc/tools/network_emulator/
Demulate.py154 emulator = network_emulator.NetworkEmulator(connection_config,
157 emulator.check_permissions()
169 emulator.emulate(external_ip)
/external/smali/smali-integration-tests/src/test/smali/junit-tests/
DTestSuite.smali7 #device/emulator, and then zip up the classes.dex containing this class
8 #and all of the tests and push that to the device/emulator.
/external/angle/src/compiler/translator/
DBuiltInFunctionEmulator.cpp19 BuiltInFunctionEmulationMarker(BuiltInFunctionEmulator &emulator) in BuiltInFunctionEmulationMarker() argument
20 : TIntermTraverser(true, false, false), mEmulator(emulator) in BuiltInFunctionEmulationMarker()
/external/gemmlowp/scripts/
Dci-test.sh4 android-wait-for-emulator
Dci-before.sh6 emulator -avd test -no-audio -no-window &
/external/perfetto/buildtools/
D.gitignore10 emulator/
/external/curl/packages/Symbian/
Dreadme.txt27 When starting curl in the Windows emulator from the Windows command-line,
34 stderr goes to the epocwind.out file (on the emulator). The standard
59 and limitations on the Windows emulator.
/external/u-boot/board/freescale/ls1088a/
DREADME65 - QSPI emulator support
133 - QSPI emulator support
/external/u-boot/board/freescale/ls2080a/
DREADME3 This is a emulator target with limited peripherals.
/external/grpc-grpc/src/android/test/interop/
DREADME.md30 requires an emulator already running on your computer.
/external/smali/examples/HelloWorld/
DHelloWorld.smali4 #To assemble and run this on a phone or emulator:
/external/autotest/server/site_tests/firmware_FlashServoKeyboardMap/
Dcontrol17 For using the keyboard emulator atmega chip on the servo v3, the keyboard
/external/u-boot/doc/driver-model/
Dpci-info.rst115 With sandbox we need a device emulator for each device on the bus since there
117 emulator driver. For example::
145 When accesses go to the pci@1f,0 device they are forwarded to its emulator.
/external/autotest/server/site_tests/brillo_StorageWriteSpeedTest/
Dcontrol.EmulatorTest15 Tests whether a Brillo emulator's storage can be written to faster than
/external/chromium-trace/catapult/devil/docs/
Dadb_wrapper.md325 Runs an emulator console command.
327 See http://developer.android.com/tools/devices/emulator.html#console
330 cmd: The command to run on the emulator console.
335 The output of the emulator console command.
/external/compiler-rt/test/
Dlit.common.configured.in27 set_default("emulator", "@COMPILER_RT_EMULATOR@")
/external/u-boot/board/kobol/helios4/
DREADME45 When download finishes start your favorite terminal emulator
/external/u-boot/drivers/tee/
DKconfig18 bool "Sandbox TEE emulator"
/external/perfetto/docs/contributing/
Dtesting.md36 1B) Start the build-in emulator (supported on Linux and MacOS):
43 2) Run the tests (either on the emulator or physical device):

1234