| 1 |
64-bit Windows on AMD64/Intel EM64T is somewhat supported in the 7.0 |
| 2 |
and later release. A collector can be built with Microsoft Visual C++ 2005 |
| 3 |
or with mingw-w64 gcc. |
| 4 |
More testing would clearly be helpful. |
| 5 |
|
| 6 |
NT_MAKEFILE has been used in this environment. Uncomment the corresponding |
| 7 |
definitions of CPU and CVTRES_CPU variables (commenting out the ones for X86), |
| 8 |
and then type "nmake -f NT_MAKEFILE" in a Visual C++ command line window to |
| 9 |
build the dynamic library with threads support and the usual test programs. |
| 10 |
To verify that the collector is at least somewhat functional, run gctest.exe. |
| 11 |
This should create gctest.gc.log after a few seconds. |
| 12 |
|
| 13 |
Test_cpp.exe might not run correctly in case of dynamic GC linking. (It seems |
| 14 |
that we're getting wrong instances of operator new/delete in some cases.) |
| 15 |
|
| 16 |
This process is completely analogous to NT_MAKEFILE usage |
| 17 |
for the 32-bit library version. |
| 18 |
|
| 19 |
A similar procedure using NT_MAKEFILE should be usable to |
| 20 |
build the static library (see comments for CFLAGS_SPECIFIC and LINK_GC |
| 21 |
variables in NT_MAKEFILE). |
| 22 |
|
| 23 |
Note that some warnings have been explicitly turned off in the makefile. |
| 24 |
|
| 25 |
VC++ note: to suppress warnings -D_CRT_SECURE_NO_DEPRECATE is used. |
| 26 |
|
| 27 |
gcc note: -fno-strict-aliasing should be used if optimizing. |