version 1.1, 2002/07/24 08:00:16 |
version 1.2, 2003/06/24 05:11:38 |
Line 25 Win32 applications compiled with some flavor of gcc cu |
|
Line 25 Win32 applications compiled with some flavor of gcc cu |
|
like win32s applications, in that dynamic library data segments are |
like win32s applications, in that dynamic library data segments are |
not scanned. (Gcc does not directly support Microsoft's "structured |
not scanned. (Gcc does not directly support Microsoft's "structured |
exception handling". It turns out that use of this feature is |
exception handling". It turns out that use of this feature is |
unavoidable if you scan arbirtray memory segments obtained from |
unavoidable if you scan arbitrary memory segments obtained from |
VirtualQuery.) |
VirtualQuery.) |
|
|
The collector test program "gctest" is linked as a GUI application, |
The collector test program "gctest" is linked as a GUI application, |
Line 65 MAKEFILE. (Make sure that the CPU environment variabl |
|
Line 65 MAKEFILE. (Make sure that the CPU environment variabl |
|
to be i386.) In order to use the gc_cpp.h C++ interface, all |
to be i386.) In order to use the gc_cpp.h C++ interface, all |
client code should include gc_cpp.h. |
client code should include gc_cpp.h. |
|
|
|
If you would prefer a VC++.NET project file, ask boehm@acm.org. One has |
|
been contributed, but it seems to contain some absolute paths etc., so |
|
it can presumably only be a starting point, and is not in the standard |
|
distribution. It is unclear (to me, Hans Boehm) whether it is feasible to |
|
change that. |
|
|
Clients may need to define GC_NOT_DLL before including gc.h, if the |
Clients may need to define GC_NOT_DLL before including gc.h, if the |
collector was built as a static library (as it normally is in the |
collector was built as a static library (as it normally is in the |
absence of thread support). |
absence of thread support). |
Line 155 To compile the collector and testing programs use the |
|
Line 161 To compile the collector and testing programs use the |
|
All programs using gc should be compiled with 4-byte alignment. |
All programs using gc should be compiled with 4-byte alignment. |
For further explanations on this see comments about Borland. |
For further explanations on this see comments about Borland. |
|
|
If gc compiled as dll, the macro ``GC_DLL'' should be defined before |
If the gc is compiled as dll, the macro ``GC_DLL'' should be defined before |
including "gc.h" (for example, with -DGC_DLL compiler option). It's |
including "gc.h" (for example, with -DGC_DLL compiler option). It's |
important, otherwise resulting programs will not run. |
important, otherwise resulting programs will not run. |
|
|