Lines Matching full:dll
314 DLL or EXE; see the description of `--export-all-symbols' below.
969 `.exe' or `.dll' suffix, this option forces the linker to copy the
1363 `--dll-verbose'
1603 output to be a dynamically linked library (DLL) instead of a normal
1604 executable. You should name the output `*.dll' when you use this
1625 `--dll'
1626 Create a DLL instead of a regular executable. You may also use
1671 If given, all global symbols in the objects used to build a DLL
1672 will be exported by the DLL. Note that this is the default if
1680 DLL's internal layout such as those beginning with `_head_' or
1714 Use VALUE as the base address of your program or dll. This is the
1715 lowest memory location that will be used when your program or dll
1766 corresponding to the DLL the linker is generating. This DEF file
1774 lib corresponding to the DLL the linker is generating. This import
1775 lib (which should be called `*.dll.a' or `*.a' may be used to link
1776 clients against the generated DLL; this behaviour makes it
1785 DLL, in-memory collisions and relocations which can delay program
1795 `--dll-search-prefix STRING'
1796 When linking dynamically to a dll without an import library,
1797 search for `<string><basename>.dll' in preference to
1798 `lib<basename>.dll'. This behaviour allows easy distinction
1801 `--dll-search-prefix=cyg'. [This option is specific to the i386
1827 to member fields of struct variables imported from a DLL, as well
1829 DLL. Any multiword variable (arrays, structs, long long, etc) may
1875 compile-time #defines to indicate whether you are building a DLL,
1876 building client code that will link to the DLL, or merely
1931 section, that is, DATA imports from DLL with non-zero offset, this
5391 libraries, which contains information for linking to dll's. They
5397 _exporting DLL symbols_
5398 The cygwin/mingw `ld' has several ways to export symbols for dll's.
5416 non-local (global and common) symbols it finds in a DLL, with
5419 desirable to export all of a DLL's symbols, which may include
5438 should be exported when a dll is created. Usually it is
5439 named `<dll name>.def' and is added as any other object file
5443 gcc -o <output> <objectfiles> <dll name>.def
5449 `xyz.dll':
5451 LIBRARY "xyz.dll" BASE=0x20000000
5457 another_foo = abc.dll.afoo
5460 This example defines a DLL with a non-default base address
5464 and treating it as an alias for `afoo' exported from the DLL
5465 `abc.dll'. The final symbol `var1' is declared to be a data
5469 name of the output DLL. If `<name>' does not include a suffix,
5470 the default library suffix, `.DLL' is appended.
5492 Declares `<name1>' as an exported symbol from the DLL, or
5495 `<external-name>' in the DLL `<module-name>'. Optionally,
5501 `NONAME': Do not put the symbol name in the DLL's export
5521 `PRIVATE': Put the symbol in the DLL's export table, but do
5525 using the GNU ld extension of linking directly to the DLL
5531 While linking a shared dll, `ld' is able to create a DEF file
5536 source code itself, so that when building the DLL each symbol
5542 All such symbols will be exported from the DLL. If, however,
5543 any of the object files in the DLL contain symbols decorated
5565 The standard Windows dll format supports data imports from dlls
5614 including data symbols, to a dll without the usage of any import
5618 import lib, each function or variable exported from the dll is
5625 Linking directly to a dll uses no extra command-line switches
5629 order to force ld to select the dll instead of an import library.
5634 libxxx.dll.a
5635 xxx.dll.a
5638 cygxxx.dll (*)
5639 libxxx.dll
5640 xxx.dll
5644 (*) Actually, this is not `cygxxx.dll' but in fact is
5645 `<prefix>xxx.dll', where `<prefix>' is set by the `ld' option
5646 `--dll-search-prefix=<prefix>'. In the case of cygwin, the
5647 standard gcc spec file includes `--dll-search-prefix=cyg', so in
5648 effect we actually search for `cygxxx.dll'.
5653 conflicts among dll's built for the various win32/un*x
5654 environments, so that (for example) two versions of a zlib dll
5658 applications and dll's and a `lib' directory for the import
5662 cygxxx.dll
5664 libxxx.dll.a (in case of dll's)
5667 Linking directly to a dll without using the import library can be
5670 1. Use the dll directly by adding the `bin' path to the link line
5673 However, as the dll's often have version numbers appended to their
5674 names (`cygncurses-5.dll') this will often fail, unless one
5678 2. Create a symbolic link from the dll to a file in the `lib'
5681 making the app/dll.
5683 ln -s bin/cygxxx.dll lib/[cyg|lib|]xxx.dll[.a]
5693 cygxxx-5.dll
5695 libxxx.dll.a -> ../bin/cygxxx-5.dll
5697 Linking directly to a dll without using an import lib will work
5705 1. Until recently, the link-directly-to-dll functionality did _not_
5710 indirection symbols that point to the exports of a dll). Again,
5715 is critical when linking against OS-supplied dll's (eg, the win32
5721 dll, in many cases, is a useful addition to the suite of tools
5733 DEF file when creating the dll. This will affect also the
5737 LIBRARY "xyz.dll" BASE=0x61000000
5761 LIBRARY "xyz.dll" BASE=0x61000000
6792 * --dll: Options. (line 1537)
6793 * --dll-search-prefix: Options. (line 1707)
7137 * direct linking to a dll: WIN32. (line 233)
7159 * exporting DLL symbols: WIN32. (line 19)
