| 1 |
64-bit Windows on AMD64/Intel EM64T (x64) is supported. A collector can be |
| 2 |
built with Microsoft Visual C++ 2005 or with mingw-w64 gcc. |
| 3 |
|
| 4 |
NT_MAKEFILE has been used in this environment. Type |
| 5 |
"nmake -f NT_MAKEFILE cpu=AMD64 nodebug=1" in a Visual C++ command line |
| 6 |
window to build the release variant of the dynamic library with threads |
| 7 |
support. |
| 8 |
To verify that the collector is at least somewhat functional, |
| 9 |
type "nmake -f NT_MAKEFILE cpu=AMD64 check" to build and run the usual test |
| 10 |
programs. This should create gctest.gc.log after a few seconds. |
| 11 |
|
| 12 |
Test_cpp.exe might not run correctly in case of dynamic GC linking. (It seems |
| 13 |
that we're getting wrong instances of operator new/delete in some cases.) |
| 14 |
|
| 15 |
This process is completely analogous to NT_MAKEFILE usage |
| 16 |
for the 32-bit library version. |
| 17 |
|
| 18 |
A similar procedure using NT_MAKEFILE is applicable to build the static |
| 19 |
library - just pass "enable_static=1" as an extra argument to nmake. |
| 20 |
If needed, it is also possible to build the library without threads |
| 21 |
support - this could be done by passing "disable_threads=1" argument to nmake. |
| 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. |