Home
last modified time | relevance | path

Searched refs:DLL (Results 1 – 25 of 91) sorted by relevance

1234

/freebsd-10-stable/contrib/libyaml/win32/vc6/
Dyamldll.dsp41 # PROP Output_Dir "Output/Release/lib/DLL"
42 # PROP Intermediate_Dir "Build/Release/lib/DLL"
56 … uuid.lib odbc32.lib odbccp32.lib /nologo /dll /machine:I386 /out:"Output/Release/lib/DLL/yaml.dll"
67 # PROP Output_Dir "Output/Debug/lib/DLL"
68 # PROP Intermediate_Dir "Build/Debug/lib/DLL"
82 ….lib odbccp32.lib /nologo /dll /debug /machine:I386 /out:"Output/Debug/lib/DLL/yaml.dll" /pdbtype:…
/freebsd-10-stable/contrib/gcc/config/arm/
DREADME-interworking166 is also possible to call Thumb code in a DLL from an ARM program and
176 When compiling files for a DLL or a program the `-mthumb-interwork'
183 If the exported functions from a DLL are all Thumb encoded then the
188 If the DLL consists of both exported Thumb functions and exported
190 Instead the Thumb functions in the DLL should be compiled with the
197 If it is possible for Thumb functions in a DLL to call
213 When linking a program with an old DLL which does not support
650 And a DLL source file (`dll.c') like this:
654 Here is how to build the DLL and the program for a purely ARM based
658 Build a `.def' file describing the DLL:
[all …]
/freebsd-10-stable/crypto/heimdal/lib/heimdal/
DNTMakefile70 DLL=$(BINDIR)\heimdal.dll
74 $(DLL): $(DLLDEPS) $(DEF) $(RES)
76 -def:$(DEF) -out:$(DLL) \
/freebsd-10-stable/contrib/file/magic/Magdir/
Depoc49 >4 lelong 0x00000000 DLL
54 >4 lelong 0x1000008D DLL
Dmsdos69 >>>(0x3c.l+22) leshort&0x2000 >0 (DLL)
154 >>>(0x3c.l+0x0c) leshort&0x8003 0x8002 (DLL)
166 >>>(0x3c.l+0x10) lelong&0x28000 =0x8000 (DLL)
968 >>>&-1 string <PIFMGR.DLL \b, icon=%s
969 #>>>&-1 string PIFMGR.DLL \b, icon=%s
970 >>>&-1 string >PIFMGR.DLL \b, icon=%s
/freebsd-10-stable/contrib/ncurses/misc/
Dmakedef.cmd35 * makedef.cmd - update a DLL export list using a newly created library file
78 * all unused data (comments, DLL directives, blanks, etc). All this
126 * this symbol was in the old DLL and it's no longer
Dcmpdef.cmd69 * First we find all public symbols from the original DLL. All this
95 * Now we find all public symbols from the new DLL, and compare.
Dchkdef.cmd67 * First we find all public symbols from the original DLL. All this
/freebsd-10-stable/contrib/llvm/tools/clang/include/clang/Driver/
DCLCompatOptions.td133 def _SLASH_LD : CLFlag<"LD">, HelpText<"Create DLL">;
134 def _SLASH_LDd : CLFlag<"LDd">, HelpText<"Create debug DLL">;
138 Flags<[CLOption, DriverOption]>, HelpText<"Use DLL run-time">;
140 Flags<[CLOption, DriverOption]>, HelpText<"Use DLL debug run-time">;
/freebsd-10-stable/contrib/gcc/config/i386/
Dcygming.opt32 Generate code for a DLL
/freebsd-10-stable/contrib/zlib/
DREADME23 <info@winimage.com> for the Windows DLL version. The zlib home page is
58 - For Windows DLL versions, please see win32/DLL_FAQ.txt
DChangeLog55 - Fix version numbers and DLL names in contrib/vstudio/*/zlib.rc
379 - Add DLL install in win32/makefile.gcc [Bar-Lev]
855 - FAQ update regarding the Windows DLL [Truta]
859 - Adapt the zlib interface to the new DLL convention guidelines [Truta]
878 - Update contrib/vstudio/vc70_32 to comply with the new DLL guidelines
899 - Synchronize zconf.h with the new Windows DLL interface [Truta]
1061 - use macro EXTERN instead of extern to support DLL for BeOS (Sander Stoks)
1217 - add EXPORT in all exported functions (for Windows DLL)
1240 - Add EXPORT keyword for check_func (needed for Windows DLL)
1246 - assign numbers to the exported functions in zlib.def (for Windows DLL)
[all …]
Dzconf.h.in332 /* If building or using zlib as a DLL, define ZLIB_DLL.
346 * Caution: the standard ZLIB1.DLL is NOT compiled using ZLIB_WINAPI.
DFAQ14 2. Where can I get a Windows DLL version?
16 The zlib sources can be compiled without change to produce a DLL. See the
18 precompiled DLL are found in the zlib web site at http://zlib.net/ .
/freebsd-10-stable/contrib/binutils/ld/
Dldint.texinfo621 With this feature on, DLL clients can import variables from DLL
631 system) So, the resulting DLL can be used with any other PE
642 (virtual/physical memory): should be less than effect of DLL
649 to make client access variable directly in the DLL, bypassing
650 the extra dereference imposed by ordinary DLL runtime linking.
656 into loaded DLL. The aim is to make OS loader do so, and than
659 from particular DLL. Each such structure points to two other
667 For each reference of data symbol to be imported from DLL (to
673 integer), pointer to DLL name (so, DLL name is referenced by
688 IMAGE_IMPORT_DESCRIPTORS for the same DLL is possible. Answer is yes,
Dld.texinfo1978 the output to be a dynamically linked library (DLL) instead of a
2008 Create a DLL instead of a regular executable. You may also use
2035 If given, all global symbols in the objects used to build a DLL will
2036 be exported by the DLL. Note that this is the default if there
2044 re-exported, nor will symbols specifying the DLL's internal layout
2142 file corresponding to the DLL the linker is generating. This DEF file
2152 import lib corresponding to the DLL the linker is generating. This
2154 may be used to link clients against the generated DLL; this behaviour
2163 from the dllname to create unique image bases for each DLL, in-memory
2204 fields of struct variables imported from a DLL, as well as using a
[all …]
/freebsd-10-stable/contrib/serf/
DSConstruct257 # Disable optimizations for debugging, use debug DLL runtime
261 # Optimize for speed, use DLL runtime
/freebsd-10-stable/contrib/binutils/binutils/doc/
Dbinutils.texi3229 @cindex DLL
3234 files such as Windows. A DLL contains an export table which contains
3240 will be in the DLL. A @file{.o} file can contain information in
3286 When creating a DLL, along with the source for the DLL, it is necessary
3291 exported from the DLL, which functions the DLL imports, and so on. This
3298 In order to mark a function as being exported from a DLL, it needs to
3310 The second file needed for DLL creation is an exports file. This file
3311 is linked with the object files that make up the body of the DLL and it
3312 handles the interface between the DLL and the outside world. This is a
3316 The third file needed for DLL creation is the library file that programs
[all …]
/freebsd-10-stable/contrib/sqlite3/
DMakefile.msc922 …$(LD) $(LDFLAGS) $(LTLINKOPTS) $(LTLIBPATHS) /DLL $(CORE_LINK_OPTS) /OUT:$@ $(LIBOBJ) $(LIBRESOBJS…
/freebsd-10-stable/contrib/binutils/
Dltoptions.m4132 _LT_DECL([], [DLLTOOL], [0], [DLL creation program])dnl
/freebsd-10-stable/contrib/binutils/ld/emultempl/
Dpep.em304 …fprintf (file, _(" --export-all-symbols Automatically export all globals to DLL\n")…
307 …fprintf (file, _(" --output-def <file> Generate a .DEF file for the built DLL\n"));
986 two import libraries for the same DLL (specifically,
1316 if (strcmp (ext, ".dll") == 0 || strcmp (ext, ".DLL") == 0)
/freebsd-10-stable/contrib/openbsm/m4/
Dltoptions.m4140 _LT_DECL([], [DLLTOOL], [1], [DLL creation program])dnl
/freebsd-10-stable/contrib/file/m4/
Dltoptions.m4140 _LT_DECL([], [DLLTOOL], [1], [DLL creation program])dnl
/freebsd-10-stable/contrib/ntp/sntp/m4/
Dltoptions.m4142 _LT_DECL([], [DLLTOOL], [1], [DLL creation program])dnl
/freebsd-10-stable/contrib/ntp/sntp/libevent/m4/
Dltoptions.m4142 _LT_DECL([], [DLLTOOL], [1], [DLL creation program])dnl

1234