The "windows" subdirectory contains scripts and support files required for the packaging process. There are NSIS scripts available to create Valgrind for Windows installation packages for 32 bit and 64 bit Windows. An installation package for 64 bit Windows supports both 32 and 64 bit applications. An installation package for 32 bit Windows supports only 32 bit applications.
This installation package must be created on a 32 bit Windows. It can not be created on 64 bit. To create the package, simply cd to "windows" and run "package32.cmd". This will strip the binaries and create a "valgrind4win32-version.exe" using the "valgrind4win32.nsi" package definition.
See "ReadMe32.txt" for details about the package contents.
This installation package must be created on a 64 bit Windows. It can not be created on 32 bit. To create the package, simply cd to "windows" and run "package64.cmd". This will strip the binaries and create a "valgrind4win64-version.exe" using the "valgrind4win64.nsi" package definition. Please note that before running this script, you must manually copy 32 bit versions of dbghelp.dll and symsrv.dll to the "windows" subdirectory.
Note that the created installer is a 32 bit application, even for the 64 bit Valgrind for Windows version. But this is ok, the resulting installer checks the bitness of the Windows and refuses to proceed if it detects an incompatible installation attempt (that is trying to install a 64 bit version on a 32 bit Windows).
When installing the 32 bit Valgrind for Windows version on a 64 bit Windows the installer shows a warning before proceeding. While it is technically possible to do this -and it is even possible to have both the 32 bit and the 64 bit version installed on the same 64 bit machine- it does not make sense, because the 64 bit version supports both 32 and 64 bit applications.
See "ReadMe64.txt" for details about the package contents.