Lines Matching full:dll
336 DLL or EXE; see the description of `--export-all-symbols' below.
1010 `.exe' or `.dll' suffix, this option forces the linker to copy the
1409 `--dll-verbose'
1649 output to be a dynamically linked library (DLL) instead of a normal
1650 executable. You should name the output `*.dll' when you use this
1671 `--dll'
1672 Create a DLL instead of a regular executable. You may also use
1723 If given, all global symbols in the objects used to build a DLL
1724 will be exported by the DLL. Note that this is the default if
1732 DLL's internal layout such as those beginning with `_head_' or
1770 Use VALUE as the base address of your program or dll. This is the
1771 lowest memory location that will be used when your program or dll
1822 corresponding to the DLL the linker is generating. This DEF file
1830 lib corresponding to the DLL the linker is generating. This import
1831 lib (which should be called `*.dll.a' or `*.a' may be used to link
1832 clients against the generated DLL; this behaviour makes it
1841 DLL, in-memory collisions and relocations which can delay program
1851 `--dll-search-prefix STRING'
1852 When linking dynamically to a dll without an import library,
1853 search for `<string><basename>.dll' in preference to
1854 `lib<basename>.dll'. This behaviour allows easy distinction
1857 `--dll-search-prefix=cyg'. [This option is specific to the i386
1883 to member fields of struct variables imported from a DLL, as well
1885 DLL. Any multiword variable (arrays, structs, long long, etc) may
1931 compile-time #defines to indicate whether you are building a DLL,
1932 building client code that will link to the DLL, or merely
1987 section, that is, DATA imports from DLL with non-zero offset, this
5536 libraries, which contains information for linking to dll's. They
5542 _exporting DLL symbols_
5543 The cygwin/mingw `ld' has several ways to export symbols for dll's.
5561 non-local (global and common) symbols it finds in a DLL, with
5564 desirable to export all of a DLL's symbols, which may include
5583 should be exported when a dll is created. Usually it is
5584 named `<dll name>.def' and is added as any other object file
5588 gcc -o <output> <objectfiles> <dll name>.def
5594 `xyz.dll':
5596 LIBRARY "xyz.dll" BASE=0x20000000
5602 another_foo = abc.dll.afoo
5607 This example defines a DLL with a non-default base address
5611 and treating it as an alias for `afoo' exported from the DLL
5612 `abc.dll'. The final symbol `var1' is declared to be a data
5619 name of the output DLL. If `<name>' does not include a suffix,
5620 the default library suffix, `.DLL' is appended.
5642 Declares `<name1>' as an exported symbol from the DLL, or
5645 `<external-name>' in the DLL `<module-name>'. Optionally,
5652 `NONAME': Do not put the symbol name in the DLL's export
5672 `PRIVATE': Put the symbol in the DLL's export table, but do
5676 using the GNU ld extension of linking directly to the DLL
5682 While linking a shared dll, `ld' is able to create a DEF file
5687 source code itself, so that when building the DLL each symbol
5693 All such symbols will be exported from the DLL. If, however,
5694 any of the object files in the DLL contain symbols decorated
5716 The standard Windows dll format supports data imports from dlls
5765 including data symbols, to a dll without the usage of any import
5769 import lib, each function or variable exported from the dll is
5776 Linking directly to a dll uses no extra command-line switches
5780 order to force ld to select the dll instead of an import library.
5785 libxxx.dll.a
5786 xxx.dll.a
5789 cygxxx.dll (*)
5790 libxxx.dll
5791 xxx.dll
5795 (*) Actually, this is not `cygxxx.dll' but in fact is
5796 `<prefix>xxx.dll', where `<prefix>' is set by the `ld' option
5797 `--dll-search-prefix=<prefix>'. In the case of cygwin, the
5798 standard gcc spec file includes `--dll-search-prefix=cyg', so in
5799 effect we actually search for `cygxxx.dll'.
5804 conflicts among dll's built for the various win32/un*x
5805 environments, so that (for example) two versions of a zlib dll
5809 applications and dll's and a `lib' directory for the import
5813 cygxxx.dll
5815 libxxx.dll.a (in case of dll's)
5818 Linking directly to a dll without using the import library can be
5821 1. Use the dll directly by adding the `bin' path to the link line
5824 However, as the dll's often have version numbers appended to their
5825 names (`cygncurses-5.dll') this will often fail, unless one
5829 2. Create a symbolic link from the dll to a file in the `lib'
5832 making the app/dll.
5834 ln -s bin/cygxxx.dll lib/[cyg|lib|]xxx.dll[.a]
5844 cygxxx-5.dll
5846 libxxx.dll.a -> ../bin/cygxxx-5.dll
5848 Linking directly to a dll without using an import lib will work
5856 1. Until recently, the link-directly-to-dll functionality did _not_
5861 indirection symbols that point to the exports of a dll). Again,
5866 is critical when linking against OS-supplied dll's (eg, the win32
5872 dll, in many cases, is a useful addition to the suite of tools
5884 DEF file when creating the dll. This will affect also the
5888 LIBRARY "xyz.dll" BASE=0x61000000
5912 LIBRARY "xyz.dll" BASE=0x61000000
7052 * --dll: Options. (line 1581)
7053 * --dll-search-prefix: Options. (line 1761)
7404 * direct linking to a dll: WIN32. (line 239)
7426 * exporting DLL symbols: WIN32. (line 19)
