![]() ![]() 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). Run NMake command: E:\pcre2-10.39\build> nmake install.the 圆4 Native Tools Command Prompt for VS 2017 and navigate to the Makefile mentioned above. The build directory should now contain a usable build system - Makefile.In the CMake GUI, the cache can be deleted by selecting "File > Delete Cache". In the event that errors occur, it is recommended that you delete the CMake cache before attempting to repeat the CMake build process. ![]() The adjacent "Generate" button should now be active. CMAKE_INSTALL_PREFIX E:\pcre2-10.39-install.Make sure the following options are selected: The GUI will then list several configuration options.Create a new, empty install directory.When specifying the generator for this project select "NMake Makefiles".Enter E:\pcre2-10.39 and E:\pcre2-10.39\build for the source and build directories, respectively.Do not try to start Cmake from the Windows Start menu, as this can lead to errors. the 圆4 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui. Create a new, empty build directory, preferably a subdirectory of the source dir.Install CMake from, during install select: and ensure that cmake\bin is on your path (tested version 3.9.4).Download PCRE or PCRE2 (supported since Zabbix 6.0) library from repository: ( ).If you want everything, use "nmake install". libraries, header files, but no documentation). Files=152, Tests=1152, 501 wallclock secs ( 0.67 usr 0.61 sys = 1.28 CPU) Result: PASS e:\openssl-1.1.1> nmake install_sw'install_sw' installs only software components (i.e. Compile OpenSSL, run tests, install: e:\openssl-1.1.1> nmake e:\openssl-1.1.1> nmake test.Disadvantage: copying Zabbix agent to another machine requires copying OpenSSL DLLs, too. Advantage: when a new OpenSSL bugfix version is released, probably you can upgrade only OpenSSL DLLs, without recompiling Zabbix agent. If 'no-shared' is not used, then the static libraries libcrypto.lib and libssl.lib will be using OpenSSL DLLs at runtime.Disadvantage: when a new OpenSSL bugfix version is released, Zabbix agent needs to recompiled and reinstalled. Advantage: Zabbix binaries can be copied to other Windows machines without OpenSSL libraries. Note the option 'no-shared': if 'no-shared' is used then the OpenSSL static libraries libcrypto.lib and libssl.lib will be 'self-sufficient' and resulting Zabbix binaries will include OpenSSL in themselves, no need for external OpenSSL DLLs.Configure OpenSSL, for example: e:\openssl-1.1.1> perl E:\openssl-1.1.1\Configure VC-WIN64A no-shared no-capieng no-srp no-gost no-dgram no-dtls1-method no-dtls1_2-method -api=1.1.0 -prefix=C:\OpenSSL-Win64-111-static -openssldir=C:\OpenSSL-Win64-111-static.Verify that NASM can be found: e:\openssl-1.1.1> nasm -version NASM version 2.13.01 compiled on May 1 2017.Go to the OpenSSL source directory, e.g.the 圆4 Native Tools Command Prompt for VS 2017 RC. Unpack OpenSSL sources, for example, in E:\openssl-1.1.1.Perl module Text::Template (cpan Text::Template).For compiling OpenSSL you will need on Windows machine:.The following steps will help you to compile OpenSSL from sources on MS Windows 10 (64-bit). This section demonstrates how to build Zabbix Windows agent binaries from sources with or without TLS. Building Zabbix agent on Windows Overview ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |