Searched
full:executables (Results
601 -
625 of
1648) sorted by null
<<21222324252627282930>>
/external/libgdx/extensions/gdx-setup/src/com/badlogic/gdx/setup/resources/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/external/libjpeg-turbo/release/ |
libjpeg-turbo.spec.in | 4 # Path under which executables should be installed
|
/external/libpng/contrib/gregbook/ |
Makefile.sgi | 19 # This makefile builds dynamically linked executables (against libpng and zlib,
|
Makefile.w32 | 28 # builds statically linked executables, but that can be changed by uncom-
|
/external/libvncserver/common/ |
md5.h | 38 the resulting executable. Locally running cross-compiled executables
|
/external/libxml2/VxWorks/ |
README | 69 static libraries and executables.
|
/external/protobuf/src/google/protobuf/stubs/ |
atomicops_internals_x86_gcc.cc | 45 // of the global offset table. To avoid breaking such executables, this code
|
/external/skia/infra/bots/flavor/ |
default_flavor.py | 158 These refer to paths on the same device where the test executables will
|
/external/skia/platform_tools/android/apps/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/external/smali/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/external/testng/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/external/toybox/ |
Config.in | 147 standard ELF binaries, and requires specially packaged executables.
|
/external/valgrind/auxprogs/ |
getoff.c | 26 In a bi-arch setup, this is used to build 2 executables
|
/external/valgrind/coregrind/ |
link_tool_exe_linux.in | 3 # This script handles linking the tool executables on Linux,
|
/external/valgrind/docs/internals/ |
qemu-mips64-linux-HOWTO.txt | 94 that can build 64 bit executables, it is necessary to install
|
/external/vboot_reference/ |
Android.mk | 118 LOCAL_MODULE_CLASS := EXECUTABLES
|
/external/vulkan-validation-layers/build-android/gradle-templates/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/external/vulkan-validation-layers/demos/smoke/android/ |
gradlew | 68 # IBM's JDK on AIX uses strange locations for the executables
|
/external/webrtc/webrtc/build/ |
apk_tests.gyp | 75 # Use webrtc copy of apk_test.gypi to allow test executables starting
|
/external/webrtc/webrtc/tools/ |
compare_videos.py | 88 script. The means the following executables have to be available in the PATH:
|
/external/zlib/src/win32/ |
DLL_FAQ.txt | 123 an implib that will cause the executables linked to it to use 219 The executables (.EXE, .DLL, etc.) that are involved in the 224 Since ZLIB1.DLL is linked to MSVCRT.DLL, the executables that 243 own separate internal state. Standalone executables and user
|
/frameworks/base/tools/layoutlib/bridge/tests/res/testApp/MyApplication/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/frameworks/compile/mclinker/include/mcld/Object/ |
ObjectLinker.h | 150 /// objects or executables
|
/frameworks/data-binding/compiler/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
/frameworks/data-binding/developmentPlugins/ |
gradlew | 73 # IBM's JDK on AIX uses strange locations for the executables
|
Completed in 897 milliseconds
<<21222324252627282930>>