| /external/openssl/crypto/dso/ |
| README | 18 and if so, convert "blah" into "blah32.dll" (the default is
19 otherwise to make it "blah.dll").
|
| /external/webkit/Source/JavaScriptCore/qt/api/ |
| qtscriptglobal.h | 25 #if defined(QT_MAKEDLL) /* create a Qt DLL library */
31 #elif defined(QT_DLL) /* use a Qt DLL library */
|
| /external/webkit/Source/WebKit/qt/Api/ |
| qwebkitglobal.h | 31 #if defined(QT_MAKEDLL) /* create a Qt DLL library */
37 #elif defined(QT_DLL) /* use a Qt DLL library */
|
| /external/chromium/base/ |
| file_version_info_unittest.cc | 36 L"FileVersionInfoTest1.dll"
40 // FileVersionInfoTest.dll
88 L"FileVersionInfoTest1.dll",
89 L"FileVersionInfoTest2.dll"
115 dll_path = dll_path.AppendASCII("FileVersionInfoTest1.dll");
|
| file_path_unittest.cc | [all...] |
| resource_util.h | 19 // Function for getting a data resource (BINDATA) from a dll. Some
|
| /external/libpng/projects/visualc71/ |
| zlib.vcproj | 12 Name="DLL Release|Win32"
30 OutputFile="$(OutDir)\zlib1.dll"
57 Name="DLL Debug|Win32"
75 OutputFile="$(OutDir)\zlib1d.dll"
102 Name="DLL ASM Release|Win32"
120 OutputFile="$(OutDir)\zlib1.dll"
147 Name="DLL ASM Debug|Win32"
165 OutputFile="$(OutDir)\zlib1d.dll"
489 Name="DLL Release|Win32"
495 Name="DLL Debug|Win32"
[all...] |
| /external/qemu/distrib/sdl-1.2.15/include/ |
| SDL_thread.h | 51 * We compile SDL into a DLL on OS/2. This means, that it's the DLL which
53 * API. There is a problem with this, that only the RTL of the SDL.DLL will
57 * start a new thread. This way, if it's the SDL.DLL which uses this API,
58 * then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /external/webkit/Source/WebCore/bindings/v8/ |
| npruntime_priv.h | 55 // plugin. Plugins load inside of a DLL. Each DLL has it's own heap. If
56 // the browser unloads the plugin DLL, all objects created within the DLL's
59 // plugin can be destroyed, which can unload the DLL. So, we must eliminate
|
| /prebuilts/tools/darwin-x86/sdl/include/SDL/ |
| SDL_thread.h | 51 * We compile SDL into a DLL on OS/2. This means, that it's the DLL which
53 * API. There is a problem with this, that only the RTL of the SDL.DLL will
57 * start a new thread. This way, if it's the SDL.DLL which uses this API,
58 * then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /prebuilts/tools/linux-x86/sdl/include/SDL/ |
| SDL_thread.h | 51 * We compile SDL into a DLL on OS/2. This means, that it's the DLL which
53 * API. There is a problem with this, that only the RTL of the SDL.DLL will
57 * start a new thread. This way, if it's the SDL.DLL which uses this API,
58 * then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /prebuilts/tools/windows/sdl/include/SDL/ |
| SDL_thread.h | 51 * We compile SDL into a DLL on OS/2. This means, that it's the DLL which
53 * API. There is a problem with this, that only the RTL of the SDL.DLL will
57 * start a new thread. This way, if it's the SDL.DLL which uses this API,
58 * then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/share/man/man1/ |
| arm-eabi-dlltool.1 | 171 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
176 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
183 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
195 The second file needed for \s-1DLL\s0 creation is an exports file. This file
196 is linked with the object files that make up the body of the \s-1DLL\s0 and it
197 handles the interface between the \s-1DLL\s0 and the outside world. This is a
201 The third file needed for \s-1DLL\s0 creation is the library file that programs
202 will link with in order to access the functions in the \s-1DLL\s0 (an `impor
[all...] |
| /prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.6/share/man/man1/ |
| arm-linux-androideabi-dlltool.1 | 171 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
176 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
183 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
195 The second file needed for \s-1DLL\s0 creation is an exports file. This file
196 is linked with the object files that make up the body of the \s-1DLL\s0 and it
197 handles the interface between the \s-1DLL\s0 and the outside world. This is a
201 The third file needed for \s-1DLL\s0 creation is the library file that programs
202 will link with in order to access the functions in the \s-1DLL\s0 (an `impor
[all...] |
| /prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/share/man/man1/ |
| arm-eabi-dlltool.1 | 171 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
176 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
183 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
195 The second file needed for \s-1DLL\s0 creation is an exports file. This file
196 is linked with the object files that make up the body of the \s-1DLL\s0 and it
197 handles the interface between the \s-1DLL\s0 and the outside world. This is a
201 The third file needed for \s-1DLL\s0 creation is the library file that programs
202 will link with in order to access the functions in the \s-1DLL\s0 (an `impor
[all...] |
| /prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/share/man/man1/ |
| arm-linux-androideabi-dlltool.1 | 171 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
176 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
183 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
195 The second file needed for \s-1DLL\s0 creation is an exports file. This file
196 is linked with the object files that make up the body of the \s-1DLL\s0 and it
197 handles the interface between the \s-1DLL\s0 and the outside world. This is a
201 The third file needed for \s-1DLL\s0 creation is the library file that programs
202 will link with in order to access the functions in the \s-1DLL\s0 (an `impor
[all...] |
| /external/protobuf/vsprojects/ |
| readme.txt | 32 issues with Win32's use of a separate heap for each DLL, as well as binary
43 2c) Change the "Configuration Type" to "Dynamic Library (.dll)".
49 do NOT install libprotobuf.dll or libprotoc.dll to any shared location.
55 If your project is itself a DLL intended for use by third-party software, we
67 1) Obtain a copy of the zlib library. The pre-compiled DLL at zlib.net works.
95 C4251 - 'identifier' : class 'type' needs to have dll-interface to be used by
104 as a DLL (see previous section). The protocol buffer library uses templates in
106 template classes from a DLL. However, in practice, it appears that exporting
108 template is available in the header files, anyone importing the DLL will jus
[all...] |
| /external/libusb_aah/msvc/ |
| listdevs.dsp | 74 # ADD BSC32 /nologo /n "../Win32/Debug/dll/core.sbr" "../Win32/Debug/dll/descriptor.sbr" "../Win32/Debug/dll/io.sbr" "../Win32/Debug/dll/sync.sbr" "../Win32/Debug/dll/poll_windows.sbr" "../Win32/Debug/dll/threads_windows.sbr" "../Win32/Debug/dll/windows_usb.sbr"
|
| /external/webkit/Source/WebKit2/win/ |
| WebKit2Common.vsprops | 19 OutputFile="$(OutDir)\$(ProjectName)$(WebKitDLLConfigSuffix).dll"
21 DelayLoadDLLs="usp10.dll;comctl32.dll;version.dll;libxslt$(LibraryConfigSuffix).dll;SQLite3$(LibraryConfigSuffix).dll;iphlpapi.dll"
|
| /external/webkit/Source/JavaScriptCore/JavaScriptCore.vcproj/ |
| JavaScriptCore.make | 19 del "%ConfigurationBuildDir%\bin\JavaScriptCore.dll"
25 -xcopy "%ConfigurationBuildDir%\bin\JavaScriptCore.dll" "$(DSTROOT)\AppleInternal\bin\" /e/v/i/h/y
26 -xcopy "%ConfigurationBuildDir%\bin\JavaScriptCore_debug.dll" "$(DSTROOT)\AppleInternal\bin\" /e/v/i/h/y
|
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/ |
| ncurses_dll.h | 36 /* "the right way" for proper static and dll+auto-import behavior */
51 /* building a DLL */
57 /* linking to the DLL */
|