| /external/libpng/projects/cbuilder5/ |
| libpng.readme.txt | 22 you wish to use zlib as a DLL, please read the important notes from
23 the zlib DLL FAQ, found inside the zlib distribution.
|
| /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...] |
| /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.12/include/ |
| SDL_thread.h | 50 We compile SDL into a DLL on OS/2. This means, that it's the DLL which
52 API. There is a problem with this, that only the RTL of the SDL.DLL will
56 start a new thread. This way, if it's the SDL.DLL which uses this API,
57 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
|
| /prebuilt/darwin-x86/sdl/include/SDL/ |
| SDL_thread.h | 50 We compile SDL into a DLL on OS/2. This means, that it's the DLL which
52 API. There is a problem with this, that only the RTL of the SDL.DLL will
56 start a new thread. This way, if it's the SDL.DLL which uses this API,
57 then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /prebuilt/linux-x86/sdl/include/SDL/ |
| SDL_thread.h | 50 We compile SDL into a DLL on OS/2. This means, that it's the DLL which
52 API. There is a problem with this, that only the RTL of the SDL.DLL will
56 start a new thread. This way, if it's the SDL.DLL which uses this API,
57 then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /prebuilt/windows/sdl/include/SDL/ |
| SDL_thread.h | 50 We compile SDL into a DLL on OS/2. This means, that it's the DLL which
52 API. There is a problem with this, that only the RTL of the SDL.DLL will
56 start a new thread. This way, if it's the SDL.DLL which uses this API,
57 then the RTL of SDL.DLL will be used to create the new thread, and if it's
|
| /prebuilt/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/share/man/man1/ |
| arm-linux-androideabi-dlltool.1 | 178 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
183 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
190 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
202 The second file needed for \s-1DLL\s0 creation is an exports file. This file
203 is linked with the object files that make up the body of the \s-1DLL\s0 and it
204 handles the interface between the \s-1DLL\s0 and the outside world. This is a
208 The third file needed for \s-1DLL\s0 creation is the library file that programs
209 will link with in order to access the functions in the \s-1DLL\s0 (an `impor
[all...] |
| /prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/share/man/man1/ |
| arm-linux-androideabi-dlltool.1 | 178 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
183 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
190 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
202 The second file needed for \s-1DLL\s0 creation is an exports file. This file
203 is linked with the object files that make up the body of the \s-1DLL\s0 and it
204 handles the interface between the \s-1DLL\s0 and the outside world. This is a
208 The third file needed for \s-1DLL\s0 creation is the library file that programs
209 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/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/bluetooth/glib/docs/reference/glib/tmpl/ |
| windows.sgml | 98 DLL name that the code being compiled will be included in.
105 @dll_name: the name of the (pointer to the) char array where the DLL name
107 <filename>windows.h</filename>. If you need a more complex DLL entry
|
| /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
|
| /external/zlib/old/visualc6/ |
| example.dsp | 20 !MESSAGE "example - Win32 DLL ASM Release" (based on "Win32 (x86) Console Application")
21 !MESSAGE "example - Win32 DLL ASM Debug" (based on "Win32 (x86) Console Application")
22 !MESSAGE "example - Win32 DLL Release" (based on "Win32 (x86) Console Application")
23 !MESSAGE "example - Win32 DLL Debug" (based on "Win32 (x86) Console Application")
37 !IF "$(CFG)" == "example - Win32 DLL ASM Release"
63 !ELSEIF "$(CFG)" == "example - Win32 DLL ASM Debug"
89 !ELSEIF "$(CFG)" == "example - Win32 DLL Release"
115 !ELSEIF "$(CFG)" == "example - Win32 DLL Debug"
249 # Name "example - Win32 DLL ASM Release"
250 # Name "example - Win32 DLL ASM Debug"
[all...] |
| minigzip.dsp | 20 !MESSAGE "minigzip - Win32 DLL ASM Release" (based on "Win32 (x86) Console Application")
21 !MESSAGE "minigzip - Win32 DLL ASM Debug" (based on "Win32 (x86) Console Application")
22 !MESSAGE "minigzip - Win32 DLL Release" (based on "Win32 (x86) Console Application")
23 !MESSAGE "minigzip - Win32 DLL Debug" (based on "Win32 (x86) Console Application")
37 !IF "$(CFG)" == "minigzip - Win32 DLL ASM Release"
63 !ELSEIF "$(CFG)" == "minigzip - Win32 DLL ASM Debug"
89 !ELSEIF "$(CFG)" == "minigzip - Win32 DLL Release"
115 !ELSEIF "$(CFG)" == "minigzip - Win32 DLL Debug"
249 # Name "minigzip - Win32 DLL ASM Release"
250 # Name "minigzip - Win32 DLL ASM Debug"
[all...] |
| /external/zlib/projects/ |
| README.projects | 17 or DLL files), these builds must be compatible to those produced by
19 In particular, if the project produces a DLL build for the Win32
20 platform, this build must comply to the officially-ammended Win32 DLL
|
| /external/zlib/projects/visualc6/ |
| example.dsp | 20 !MESSAGE "example - Win32 DLL ASM Release" (based on "Win32 (x86) Console Application")
21 !MESSAGE "example - Win32 DLL ASM Debug" (based on "Win32 (x86) Console Application")
22 !MESSAGE "example - Win32 DLL Release" (based on "Win32 (x86) Console Application")
23 !MESSAGE "example - Win32 DLL Debug" (based on "Win32 (x86) Console Application")
37 !IF "$(CFG)" == "example - Win32 DLL ASM Release"
63 !ELSEIF "$(CFG)" == "example - Win32 DLL ASM Debug"
89 !ELSEIF "$(CFG)" == "example - Win32 DLL Release"
115 !ELSEIF "$(CFG)" == "example - Win32 DLL Debug"
249 # Name "example - Win32 DLL ASM Release"
250 # Name "example - Win32 DLL ASM Debug"
[all...] |
| minigzip.dsp | 20 !MESSAGE "minigzip - Win32 DLL ASM Release" (based on "Win32 (x86) Console Application")
21 !MESSAGE "minigzip - Win32 DLL ASM Debug" (based on "Win32 (x86) Console Application")
22 !MESSAGE "minigzip - Win32 DLL Release" (based on "Win32 (x86) Console Application")
23 !MESSAGE "minigzip - Win32 DLL Debug" (based on "Win32 (x86) Console Application")
37 !IF "$(CFG)" == "minigzip - Win32 DLL ASM Release"
63 !ELSEIF "$(CFG)" == "minigzip - Win32 DLL ASM Debug"
89 !ELSEIF "$(CFG)" == "minigzip - Win32 DLL Release"
115 !ELSEIF "$(CFG)" == "minigzip - Win32 DLL Debug"
249 # Name "minigzip - Win32 DLL ASM Release"
250 # Name "minigzip - Win32 DLL ASM Debug"
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.2.1/man/man1/ |
| arm-eabi-dlltool.1 | 166 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
171 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
178 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
192 The second file needed for \s-1DLL\s0 creation is an exports file. This file
193 is linked with the object files that make up the body of the \s-1DLL\s0 and it
194 handles the interface between the \s-1DLL\s0 and the outside world. This is a
198 The third file needed for \s-1DLL\s0 creation is the library file that programs
199 will link with in order to access the functions in the \s-1DLL\s0. This fil
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.3.1/man/man1/ |
| arm-eabi-dlltool.1 | 166 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
171 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
178 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
192 The second file needed for \s-1DLL\s0 creation is an exports file. This file
193 is linked with the object files that make up the body of the \s-1DLL\s0 and it
194 handles the interface between the \s-1DLL\s0 and the outside world. This is a
198 The third file needed for \s-1DLL\s0 creation is the library file that programs
199 will link with in order to access the functions in the \s-1DLL\s0. This fil
[all...] |
