Zabbix Documentation 3.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:installation:install:win_agent

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:installation:install:win_agent [2018/11/15 14:42]
viktors.tjarve [Compiling Zabbix] fixed typo
manual:installation:install:win_agent [2019/04/08 08:50] (current)
martins-v some reformatting
Line 37: Line 37:
 </​code>'​install_sw'​ installs only software components (i.e. libraries, header files, but no documentation). If you want everything, use %%"​%%nmake install%%"​%%. </​code>'​install_sw'​ installs only software components (i.e. libraries, header files, but no documentation). If you want everything, use %%"​%%nmake install%%"​%%.
  
-=== Compiling Zabbix ===+=== Compiling Zabbix ​with OpenSSL ​===
  
 The following steps will help you to compile Zabbix from sources on MS Windows 10 (64-bit). When compiling Zabbix with/​without TLS support the only significant difference is in step 4. The following steps will help you to compile Zabbix from sources on MS Windows 10 (64-bit). When compiling Zabbix with/​without TLS support the only significant difference is in step 4.
Line 44: Line 44:
  
   - On a Linux machine check out the source from SVN:<​code>​   - On a Linux machine check out the source from SVN:<​code>​
-$ svn co svn://​svn.zabbix.com/​tags/​3.0.23 +$ svn co svn://​svn.zabbix.com/​tags/​3.0.24 
-$ cd 3.0.23/+$ cd 3.0.24/
 $ ./​bootstrap.sh $ ./​bootstrap.sh
 $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd` $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd`
Line 51: Line 51:
 $ make dist $ make dist
 </​code>​ </​code>​
-  - Copy and unpack the archive, e.g. zabbix-3.0.23.tar.gz, on a Windows machine. +  - Copy and unpack the archive, e.g. zabbix-3.0.24.tar.gz, on a Windows machine. 
-  - Let's assume that sources are in e:​\zabbix-3.0.23. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. Go to e:\3.0.23\build\win32\project.+  - Let's assume that sources are in e:​\zabbix-3.0.24. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. Go to e:\3.0.24\build\win32\project.
   - Compile zabbix_get, zabbix_sender and zabbix_agent.   - Compile zabbix_get, zabbix_sender and zabbix_agent.
     * without TLS: <​code>​     * without TLS: <​code>​
-E:\ zabbix-3.0.23\build\win32\project>​ nmake /K+E:​\zabbix-3.0.24\build\win32\project>​ nmake /K
 </​code>​ </​code>​
     * with TLS: <​code>​     * with TLS: <​code>​
-E:\ zabbix-3.0.23\build\win32\project>​ nmake /K -f Makefile_get TLS=openssl TLSINCDIR="​C:​\OpenSSL-Win64-111-static\include"​ TLSLIBDIR="​C:​\OpenSSL-Win64-111-static\lib"​ +E:​\zabbix-3.0.24\build\win32\project>​ nmake /K -f Makefile_get TLS=openssl TLSINCDIR="​C:​\OpenSSL-Win64-111-static\include"​ TLSLIBDIR="​C:​\OpenSSL-Win64-111-static\lib"​ 
-E:\ zabbix-3.0.23\build\win32\project>​ nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="​C:​\OpenSSL-Win64-111-static\include"​ TLSLIBDIR="​C:​\OpenSSL-Win64-111-static\lib"​ +E:​\zabbix-3.0.24\build\win32\project>​ nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="​C:​\OpenSSL-Win64-111-static\include"​ TLSLIBDIR="​C:​\OpenSSL-Win64-111-static\lib"​ 
-E:\ zabbix-3.0.23\build\win32\project>​ nmake /K -f Makefile_agent TLS=openssl TLSINCDIR="​C:​\OpenSSL-Win64-111-static\include"​ TLSLIBDIR="​C:​\OpenSSL-Win64-111-static\lib"​+E:​\zabbix-3.0.24\build\win32\project>​ nmake /K -f Makefile_agent TLS=openssl TLSINCDIR="​C:​\OpenSSL-Win64-111-static\include"​ TLSLIBDIR="​C:​\OpenSSL-Win64-111-static\lib"​
 </​code>​ </​code>​
-  - New binaries are located in e:​\zabbix-3.0.23\bin\win64. Since OpenSSL was compiled with '​no-shared'​ option, Zabbix binaries contain OpenSSL within themselves and can be copied to other machines that do not have OpenSSL.+  - New binaries are located in e:​\zabbix-3.0.24\bin\win64. Since OpenSSL was compiled with '​no-shared'​ option, Zabbix binaries contain OpenSSL within themselves and can be copied to other machines that do not have OpenSSL. 
 + 
 +=== Compiling Zabbix with LibreSSL === 
 + 
 +The process is similar to compiling with OpenSSL, but you need to make small changes in files located in the ''​build\win32\project''​ directory:​ 
 +    * In ''​Makefile_tls''​ delete ''/​DHAVE_OPENSSL_WITH_PSK''​. i.e. find <​code>​ 
 +CFLAGS = $(CFLAGS) /​DHAVE_OPENSSL /​DHAVE_OPENSSL_WITH_PSK</​code>​and replace it with <​code>​ 
 +CFLAGS = $(CFLAGS) /​DHAVE_OPENSSL</​code>​ 
 +    * In ''​Makefile_common.inc''​ add ''/​NODEFAULTLIB:​LIBCMT''​ i.e. find <​code>​ 
 +/​MANIFESTUAC:"​level='​asInvoker'​ uiAccess='​false'"​ /​DYNAMICBASE:​NO /​PDB:​$(TARGETDIR)\$(TARGETNAME).pdb</​code>​and replace it with <​code>​ 
 +/​MANIFESTUAC:"​level='​asInvoker'​ uiAccess='​false'"​ /​DYNAMICBASE:​NO /​PDB:​$(TARGETDIR)\$(TARGETNAME).pdb /​NODEFAULTLIB:​LIBCMT</​code>​