mingw-ldd

DLL dependency listing utility for MinGW applications

Synopsis

ldd { exename | dllname } ...

mingw32-ldd { exename | dllname } ...

Description

mingw-ldd is a Bourne shell utility script, which may be used to display the DLL dependencies of one or more MS-Windows executable programs, or other MS-Windows DLLs. Suitable for use on MS-Windows itself, (running within MinGW.org's MSYS environment), or as a component of a cross-compiler tool suite, running on a non-Windows platform, it utilizes the objdump -x utility, in conjunction with awk, to extract any DLL Name headers from the named executables, or DLLs, then recursively processes each DLL, identified as a dependency by such headers, presenting all recursively identified DLLs in the form of a dependency tree.

Typically, when deployed on MS-Windows, in the MSYS environment, this utility is simply called ldd, and is invoked using the first form of the command, as shown in the synopsis; when deployed on any non-Windows platform, to avoid conflict with the native utility of the same name, this utility is called mingw32­-ldd, (possibly with the "mingw32" prefix adjusted to match that of the mingw32-gcc command, within the associated cross-compiler suite), and is invoked using the second form of the command.

Installation

To install mingw-ldd, for use in MinGW.org's MSYS environment, simply copy the mingw32-ldd.sh file, saving it to the MSYS /bin directory, as /bin/ldd; it may then be invoked, (provided that the MinGW GCC and binutils tools, and the MSYS awk package, are also installed), using the first form shown in the synopsis.

To install on a non-Windows platform, to accompany a cross-compiler tool suite, copy the mingw32-ldd.sh file to any convenient directory in $PATH, (typically the same directory as the mingw32-gcc program itself), saving it without the .sh suffix, and make it executable, (e.g. by running chmod a+x mingw32-ldd in the appropriate directory); it may then be invoked using the second form of the command, as shown in the synopsis.

Configuration

mingw-ldd uses a small number of shell variables, to influence its configuration; these may be defined as environment variables, and passed through the shell environment when invoking mingw32-ldd; alternatively, they may be defined as script variables, in the user-specific $HOME/.mingw32rt configuration file, which will be sourced by mingw32-ldd, on start-up.

The influential variables are:—

• DLLPATH
  Specifies an aggregate colon separated list of directories, in which mingw32-ldd will search for those DLLs which are to be recursively scanned for nested dependencies. DLLPATH is normally left unspecified, thus becoming the default aggregate of "DLLPATH=$PROGRAM_FILES:/mingw/bin:$SYSTEM_DLLPATH", as defined below.

• SYSTEM_DRIVE
  Specifies a representation of the path to the root of the primary system disk drive. Under MS-Windows, this would typically be "C:", (or the effective value of Windows' own "%SYSTEMDRIVE%" variable), but should be expressed in MSYS path name syntax, (e.g. "SYSTEM_DRIVE=/c"). On non-Windows hosts, this may be used to specify, for example, the root drive of an emulated Windows installation, under Wine, (e.g. "SYSTEM_DRIVE=$HOME/.wine/drive_c").
  It is generally safe to leave the SYSTEM_DRIVE variable unspecified, (which is its default).

• SYSTEM_DLLPATH
  Specifies a colon separated list of directory paths, (in addition to /mingw/bin, which is always searched unless overridden by an explicit DLLPATH assignment), in which mingw32-ldd will search for those DLLs which are identified as dependencies; when an identified dependency matches a DLL found in any directory in this path list, (with the search terminating at the first match), that DLL will be processed recursively, to identify further nested dependencies.
  If SYSTEM_DLLPATH is unspecified, a default of "SYSTEM_DLLPATH=$SYSTEM_DRIVE/windows/system32" is assumed.

• PROGRAM_FILES
  Specifies an additional colon separated list of directory paths, which will be searched before /mingw/bin, for DLLs which are identified as dependencies; if unspecified, it is assigned a default of "PROGRAM_FILES="$SYSTEM_DRIVE/program files".

Note that the directories within "$PATH" are not automatically included within "$DLLPATH", but may be explicitly added to either PROGRAM_FILES, or SYSTEM_DLLPATH, (or to an explicit definition of DLLPATH itself), if desired.

Release Files

Recent Commits

• R/O
• R/O (HTTP)
• R/W (SSH)
• R/W (HTTPS)

Fork

提交 檔案樹 下載 待辦事項

修訂.	時間	作者	訊息 RSS
2b4c7d12	2020-09-10 04:37:28	Keith Marshall	Avoid the use of GNU-specific awk extensions. * mingw32-...
66b69666	2020-09-08 19:08:30	Keith Marshall	Support a configurable command name host prefix. * mingw...
a9475f38	2020-09-08 03:13:38	Keith Marshall	Adopt a consistent style for shell function definitions. ...
6c62748f	2020-09-07 02:38:10	Keith Marshall	Support persistent user-specific run-time initialization....
4438871e	2019-10-12 20:36:38	Keith Marshall	Use mingw32-specific objdump command, if available. * mi...
a80f93b3	2020-09-06 18:43:32	Keith Marshall	Diagnose missing files at top level. * mingw32-ldd.sh (s...
61e5b061	2017-07-22 06:14:52	Keith Marshall	New repository; initial commit. * mingw32-ldd.sh: New fi...

• more →

Most Recently Updated Tickets