summaryrefslogtreecommitdiffstats
path: root/winsup/doc/how-programming.texinfo
diff options
context:
space:
mode:
Diffstat (limited to 'winsup/doc/how-programming.texinfo')
-rw-r--r--winsup/doc/how-programming.texinfo18
1 files changed, 15 insertions, 3 deletions
diff --git a/winsup/doc/how-programming.texinfo b/winsup/doc/how-programming.texinfo
index d5b865aaa..fe20ddda3 100644
--- a/winsup/doc/how-programming.texinfo
+++ b/winsup/doc/how-programming.texinfo
@@ -241,10 +241,22 @@ gcc as:
@subsection How can I find out which dlls are needed by an executable?
-@strong{(Please note: This section has not yet been updated for the latest
-net release.)}
+@samp{objdump -p} provides this information, but is rather verbose.
+
+@samp{cygcheck} will do this much more concisely, provided the command
+is in your path.
+
+Note there is currently a bug in cygcheck in that it will not report
+on a program in a Windows system dir (e.g., C:\Windows or C:\WINNT) even
+if it's in your path. To work around this, supply the full Win32 path
+to the executable, including the .exe extension:
+
+@example
+cygcheck c:\\winnt\\system32\\cmd.exe
+@end example
-objdump -p provides this information.
+(Note the windows path separator must be escaped if this is typed in
+bash.)
@subsection How do I build a DLL?