summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorivmai <ivmai>2010-04-09 10:32:48 +0200
committerIvan Maidanski <ivmai@mail.ru>2011-07-26 19:06:53 +0200
commit79d36f80ed7e7df5deaef7c3c1c853b392749fdb (patch)
tree1383b1e9b2278790a5477e19393f6c76625b278a /doc
parente9374e1f28307eb693d429b9c141df11580a9a1a (diff)
2010-04-09 Ivan Maidanski <ivmai@mail.ru>
* NT_MAKEFILE: Remove the comment about DLL and Win32S. * NT_STATIC_THREADS_MAKEFILE: Ditto. * NT_X64_STATIC_THREADS_MAKEFILE: Ditto. * NT_MAKEFILE: Add ".SUFFIXES" directive (to handle gc_cpp.cc properly on VS 2005+). * NT_MAKEFILE: Update GC log file name in comments. * NT_STATIC_THREADS_MAKEFILE: Ditto. * NT_X64_STATIC_THREADS_MAKEFILE: Ditto. * NT_X64_THREADS_MAKEFILE: Ditto. * doc/README.win32: Ditto. * NT_MAKEFILE: Remove ":full" for "-debug" option (since no longer supported by VS). * NT_STATIC_THREADS_MAKEFILE: Ditto. * NT_MAKEFILE: Commented out copying of gc_cpp.cc to gc_cpp.cpp. * NT_STATIC_THREADS_MAKEFILE: Ditto. * NT_X64_STATIC_THREADS_MAKEFILE: Ditto. * NT_X64_THREADS_MAKEFILE: Ditto. * NT_STATIC_THREADS_MAKEFILE: Add -D PARALLEL_MARK option. * NT_STATIC_THREADS_MAKEFILE: Increase stack size for gctest.exe. * NT_X64_STATIC_THREADS_MAKEFILE: Remove "-stack" option (use the default stack size limit). * NT_X64_THREADS_MAKEFILE: Rename "gc64_dll.dll" to "gc64.dll". * win32_threads.c (GC_get_next_stack): Always define (since it is also used for Cygwin now).
Diffstat (limited to 'doc')
-rw-r--r--doc/README.win322
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/README.win32 b/doc/README.win32
index 47699e1..e93df25 100644
--- a/doc/README.win32
+++ b/doc/README.win32
@@ -49,7 +49,7 @@ client code should include gc_cpp.h.
For historical reasons,
the collector test program "gctest" is linked as a GUI application,
but does not open any windows. Its output appears in the file
-"gc.log". It may be started from the file manager. The hour glass
+"gctest.gc.log". It may be started from the file manager. The hour glass
cursor may appear as long as it's running. If it is started from the
command line, it will usually run in the background. Wait a few
minutes (a few seconds on a modern machine) before you check the output.