HomeSort by relevance Sort by last modified time
    Searched full:prereq (Results 176 - 200 of 236) sorted by null

1 2 3 4 5 6 78 910

  /external/valgrind/main/gdbserver_tests/
mssnapshot.vgtest 2 prereq: test -e gdb
mcbreak.vgtest 3 prereq: test -e gdb -a -f gdb.step
mcsigpass.vgtest 2 prereq: test -e gdb
nlpasssigalrm.vgtest 10 prereq: test -e gdb
mcinvokeWS.vgtest 7 prereq: test -f vgdb.ptraceinvoker
mcleak.vgtest 4 prereq: test -e gdb
mcmain_pic.vgtest 6 prereq: test -e gdb.pic
mcsignopass.vgtest 7 prereq: test -e gdb
mcwatchpoints.vgtest 4 prereq: test -e gdb -a -f gdb.step
nlcontrolc.vgtest 13 prereq: test -e gdb -a -f vgdb.ptraceinvoker
nlsigvgdb.vgtest 10 prereq: test -e gdb -a -f vgdb.ptraceinvoker
mcinfcallRU.vgtest 10 prereq: test -e gdb && ../tests/os_test linux
mcinfcallWSRU.vgtest 10 prereq: test -e gdb -a -f gdb.step && ../tests/os_test linux
mcinvokeRU.vgtest 7 # as the Valgrind process is always busy, we do not need the vgdb.ptraceinvoker prereq.
  /external/valgrind/main/none/tests/
empty-exe.vgtest 6 prereq: touch empty-exe && chmod u+x empty-exe
  /sdk/anttasks/src/com/android/ant/
DependencyGraph.java 194 System.out.println("PREREQ: " + path);
209 * This looks at the input paths, not at the list of known prereq. Therefore this
211 * prereq file list so that we can process those in a 2nd step.
214 * will process the remaining files in the prereq list.
319 * Check all the prereq files we know about to make sure they're still there, or that they
330 // Loop through our prereq files and make sure they still exist
331 for (File prereq : mPrereqs) {
332 if (prereq.exists() == false) {
334 System.out.println("MISSING FILE: " + prereq.getAbsolutePath());
342 String filePath = prereq.getAbsolutePath()
    [all...]
  /tools/build/builder/src/main/java/com/android/builder/compiler/
DependencyGraph.java 193 mLogger.info("PREREQ: " + path);
208 * This looks at the input paths, not at the list of known prereq. Therefore this
210 * prereq file list so that we can process those in a 2nd step.
213 * will process the remaining files in the prereq list.
318 * Check all the prereq files we know about to make sure they're still there, or that they
329 // Loop through our prereq files and make sure they still exist
330 for (File prereq : mPrereqs) {
331 if (prereq.exists() == false) {
333 mLogger.info("MISSING FILE: " + prereq.getAbsolutePath());
341 String filePath = prereq.getAbsolutePath()
    [all...]
  /tools/motodev/src/help/studio_help/src/topics/
t_device-starting_android.dita 15 <prereq>You must have an existing AVD, listed in the Device Management view. </prereq>
t_config-for-native.dita 16 <prereq>Native support requires that the following be installed:<ul>
25 Studio for Android Installation Guide</i>.</p></prereq>
t_device-screen-capturing.dita 14 <prereq>If capturing the screen on a physical device, that device must be connected to your development computer and
17 >Android Virtual Device</uicontrol>. </prereq>
t_db-table-creating.dita 14 <prereq>You perform this task from within the MOTODEV Database Explorer view. This view is part of the MOTODEV
15 Database perspective; switch to this perspective when working with Android databases.</prereq>
t_keystore-deleting.dita 14 <prereq>Deleting a keystore deletes all of the keys within that keystore as well. Before deleting any keystore,
18 copies of all keys you have used to sign apps submitted to Google Play.</note></prereq>
t_app-cert-signing_android.dita 18 <prereq>Note that this procedure requires that you have an Android Package (APK) file for each application being
19 signed. As well, the key must already be known to MOTODEV Studio for Android.</prereq>
t_app-debugging_android.dita 17 <prereq>In order to debug your application, you need to have a target device defined. To debug on an emulated
21 and connected to it using the <tm tmtype="tm">DeviceAnywhere</tm> service-->.</prereq>
t_app-deploying_android.dita 15 <prereq>
19 </prereq>

Completed in 180 milliseconds

1 2 3 4 5 6 78 910