mirror of https://github.com/Cisco-Talos/clamav
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
![]() |
15 years ago | |
---|---|---|
.. | ||
3rdparty | 16 years ago | |
compat | 15 years ago | |
llvmbuild | 16 years ago | |
res | 15 years ago | |
.gitignore | 16 years ago | |
ClamAV.sln | 15 years ago | |
LLVMcodegen.vcproj | 15 years ago | |
LLVMjit.vcproj | 15 years ago | |
LLVMsystem.vcproj | 16 years ago | |
LLVMx86codegen.vcproj | 15 years ago | |
README | 15 years ago | |
clamav-config.h | 15 years ago | |
clambc.vcproj | 16 years ago | |
clamconf.vcproj | 16 years ago | |
clamd.vcproj | 15 years ago | |
clamdscan.vcproj | 15 years ago | |
clamscan.vcproj | 15 years ago | |
configure.bat | 16 years ago | |
configure.js | 16 years ago | |
freshclam.vcproj | 16 years ago | |
libclamav.def | 15 years ago | |
libclamav.vcproj | 15 years ago | |
libclamavcxx.vcproj | 15 years ago | |
libclamunrar.def | 16 years ago | |
libclamunrar.vcproj | 16 years ago | |
libclamunrar_iface.def | 16 years ago | |
libclamunrar_iface.vcproj | 16 years ago | |
platform.h | 15 years ago | |
sigtool.vcproj | 15 years ago | |
target.h | 16 years ago | |
update-win32.pl | 15 years ago |
README
ClamAV for Win32
----------------
0- Requirements
To build the source code you will need:
- Git for windows with a git "shell"
- Microsoft Visual Studio 2008 (the express version is just fine)
To run the binaries at least Windows 2000 is required. Microsoft Visual C++ 2008
runtime libraries needs to be installed on the system. See:
http://www.microsoft.com/downloads/details.aspx?familyid=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en
1- Getting the code
The win32 source code is merged in the ClamAV repository and is available
via git.
Clone the repository with: git clone git://git.clamav.net/git/clamav-devel
See http://www.clamav.net/download/sources for more info.
2- Code configuration
After downloading the source code, minimal configuration is required:
just run the win32/configure.bat script *from within the git shell*.
Skip this step if you are building from an official release tarball.
3- Compilation
Open win32/ClamAV.sln in Visual Studio and build all.
The output directory for the binaries is either /win32/Debug or /win32/Release,
depending on the configuration you pick.
4- Special notes
The ClamAV tools in win32 are the same as in unix, so refer to their respective
manpage for general usage.
The major differences are listed below:
- Config files path search order:
1- The content of the registry key "HKEY_LOCAL_MACHINE/Software/ClamAV/ConfDir"
2- The directory where libclamav.dll is located
3- "C:\ClamAV"
- Database files path search order:
1- The content of the registry key "HKEY_LOCAL_MACHINE/Software/ClamAV/DataDir"
2- The directory "database" inside the directory where libclamav.dll is located
3- "C:\ClamAV\db"
- Globbing
Since the windows command prompt doesn't take care of wildcard expansion, minimal
emulation of unix glob() is performed internally. It supports "*" and "?" only.
- File paths
Please always use the backslash as the path separator.
SMB Network shares and UNC paths are supported.
- Debug builds
Malloc in debug (as opposed to release) mode fails after allocating some 90k
chunks; such builds won't be able to handle large databases.
Just do yourself a favour and always build in release mode.