Home | History | Annotate | Download | only in info

Lines Matching full:dll

934      `.exe' or `.dll' suffix, this option forces the linker to copy the
1313 `--dll-verbose'
1546 output to be a dynamically linked library (DLL) instead of a normal
1547 executable. You should name the output `*.dll' when you use this
1568 `--dll'
1569 Create a DLL instead of a regular executable. You may also use
1592 If given, all global symbols in the objects used to build a DLL
1593 will be exported by the DLL. Note that this is the default if
1601 DLL's internal layout such as those beginning with `_head_' or
1635 Use VALUE as the base address of your program or dll. This is the
1636 lowest memory location that will be used when your program or dll
1687 corresponding to the DLL the linker is generating. This DEF file
1695 lib corresponding to the DLL the linker is generating. This import
1696 lib (which should be called `*.dll.a' or `*.a' may be used to link
1697 clients against the generated DLL; this behaviour makes it
1706 DLL, in-memory collisions and relocations which can delay program
1716 `--dll-search-prefix STRING'
1717 When linking dynamically to a dll without an import library,
1718 search for `<string><basename>.dll' in preference to
1719 `lib<basename>.dll'. This behaviour allows easy distinction
1722 `--dll-search-prefix=cyg'. [This option is specific to the i386
1748 to member fields of struct variables imported from a DLL, as well
1750 DLL. Any multiword variable (arrays, structs, long long, etc) may
1796 compile-time #defines to indicate whether you are building a DLL,
1797 building client code that will link to the DLL, or merely
1852 section, that is, DATA imports from DLL with non-zero offset, this
5063 libraries, which contains information for linking to dll's. They
5069 _exporting DLL symbols_
5070 The cygwin/mingw `ld' has several ways to export symbols for dll's.
5095 should be exported when a dll is created. Usually it is
5096 named `<dll name>.def' and is added as any other object file
5100 gcc -o <output> <objectfiles> <dll name>.def
5106 `xyz.dll':
5108 LIBRARY "xyz.dll" BASE=0x20000000
5114 another_foo = abc.dll.afoo
5117 This example defines a DLL with a non-default base address
5121 and treating it as an alias for `afoo' exported from the DLL
5122 `abc.dll'. The final symbol `var1' is declared to be a data
5126 name of the output DLL. If `<name>' does not include a suffix,
5127 the default library suffix, `.DLL' is appended.
5149 Declares `<name1>' as an exported symbol from the DLL, or
5152 `<external-name>' in the DLL `<module-name>'. Optionally,
5158 `NONAME': Do not put the symbol name in the DLL's export
5178 `PRIVATE': Put the symbol in the DLL's export table, but do
5182 using the GNU ld extension of linking directly to the DLL
5188 While linking a shared dll, `ld' is able to create a DEF file
5193 source code itself, so that when building the DLL each symbol
5199 All such symbols will be exported from the DLL. If, however,
5200 any of the object files in the DLL contain symbols decorated
5222 The standard Windows dll format supports data imports from dlls
5271 including data symbols, to a dll without the usage of any import
5275 import lib, each function or variable exported from the dll is
5282 Linking directly to a dll uses no extra command-line switches
5286 order to force ld to select the dll instead of an import library.
5291 libxxx.dll.a
5292 xxx.dll.a
5295 cygxxx.dll (*)
5296 libxxx.dll
5297 xxx.dll
5301 (*) Actually, this is not `cygxxx.dll' but in fact is
5302 `<prefix>xxx.dll', where `<prefix>' is set by the `ld' option
5303 `--dll-search-prefix=<prefix>'. In the case of cygwin, the
5304 standard gcc spec file includes `--dll-search-prefix=cyg', so in
5305 effect we actually search for `cygxxx.dll'.
5310 conflicts among dll's built for the various win32/un*x
5311 environments, so that (for example) two versions of a zlib dll
5315 applications and dll's and a `lib' directory for the import
5319 cygxxx.dll
5321 libxxx.dll.a (in case of dll's)
5324 Linking directly to a dll without using the import library can be
5327 1. Use the dll directly by adding the `bin' path to the link line
5330 However, as the dll's often have version numbers appended to their
5331 names (`cygncurses-5.dll') this will often fail, unless one
5335 2. Create a symbolic link from the dll to a file in the `lib'
5338 making the app/dll.
5340 ln -s bin/cygxxx.dll lib/[cyg|lib|]xxx.dll[.a]
5350 cygxxx-5.dll
5352 libxxx.dll.a -> ../bin/cygxxx-5.dll
5354 Linking directly to a dll without using an import lib will work
5362 1. Until recently, the link-directly-to-dll functionality did _not_
5367 indirection symbols that point to the exports of a dll). Again,
5372 is critical when linking against OS-supplied dll's (eg, the win32
5378 dll, in many cases, is a useful addition to the suite of tools
5390 DEF file when creating the dll. This will affect also the
5394 LIBRARY "xyz.dll" BASE=0x61000000
5418 LIBRARY "xyz.dll" BASE=0x61000000
6437 * --dll: Options. (line 1480)
6438 * --dll-search-prefix: Options. (line 1628)
6759 * direct linking to a dll: WIN32. (line 218)
6781 * exporting DLL symbols: WIN32. (line 19)