zabbix软件包
移植的基础 (The basics of porting)
Originally, Buildroot offers a limited number of packages. It makes sense — there is everything you need, but any other packages can be added.
最初，Buildroot提供的软件包数量有限。 这很有意义-有您需要的一切，但可以添加任何其他软件包。
To add a package, create 2 description files, an optional checksum file, and add a link to the package in the general package list. There are hooks at different stages of the build. At the same time, Buildroot can recognize the needed type of packages:
要添加软件包，请创建2个描述文件，一个可选的校验和文件，然后在常规软件包列表中添加指向该软件包的链接。 在构建的不同阶段都有钩子。 同时，Buildroot可以识别所需的软件包类型：
- General — the general type packages. In this case, all the commands for the Assembly/installation are written on your own. 常规-常规类型包。 在这种情况下，所有用于组装/安装的命令均由您自己编写。
- Autotools, CMake, Python, Lua, Perl, rebar, waf, meson, cargo(rust), go — easy to collect packages corresponding to their names. Autotools，CMake，Python，Lua，Perl，钢筋，waf，介子，货运(锈)，去—轻松收集与它们的名称相对应的软件包。
- Virtual-packages. This is a type of package that allows you to add functionality provided by one or more packages. For example, OpenGL ES is an API for 2D and 3D graphics in embedded systems. The implementation of this API differs for Allwinner, Tech Sunxi, and Texas Instruments OMAP35xx platforms. Thus, libgles will be a virtual package, and sunxi-mali and ti-gfx will be suppliers. 虚拟包。 这是一种软件包，可让您添加一个或多个软件包提供的功能。 例如，OpenGL ES是用于嵌入式系统中2D和3D图形的API。 对于Allwinner，Tech Sunxi和Texas Instruments OMAP35xx平台，此API的实现有所不同。 因此，诽谤将是一个虚拟软件包，sunxi-mali和ti-gfx将成为供应商。
- CKonfig — packages. These are packages that support configuration via kconfig. For example, busybox and Linux-kernel. CKonfig-软件包。 这些是支持通过kconfig配置的软件包。 例如，busybox和Linux内核。
- Kernel module — a separate type of package for creating your own kernel modules. 内核模块—一种单独的软件包类型，用于创建您自己的内核模块。
Asciidoc — a type of packages for rendering documents from aciidoc to PDF, HTML, and other formats.
Asciidoc-一种用于将文档从aciidoc转换为PDF，HTML和其他格式的软件包。
There is also an infrastructure for building Linux-kernel-extensions and Linux-kernel-extensions.
还有一个用于构建Linux内核扩展和Linux内核扩展的基础架构。
All package types are well documented in the Buildroot guide. You can specify different options for getting package source — git, svn, local storage, and others. It's easy to get sources from GitHub. When porting the slim and GitHub packages, we will do so. There is a division into host packages (used only for building other packages that do not fall into the target file system) and packages that fall into the system being built. You can combine this functionality in one package.
所有软件包类型在Buildroot指南中都有详细记录。 您可以指定用于获取软件包源的其他选项-git，svn，本地存储等。 从GitHub获取资源很容易。 在移植slim和GitHub软件包时，我们会这样做。 分为主机软件包(仅用于构建不属于目标文件系统的其他软件包)和属于正在构建的系统的软件包。 您可以将此功能组合在一个软件包中。
将补丁添加到源包 (Adding patches to the source packages)
Sometimes, you need to apply patches to the source packages. There are two ways to do this:
有时，您需要将补丁应用于源软件包。 有两种方法可以做到这一点：
- By adding the patch directly to the folder with the package description (${buildroot_root_dir}/package/${packagename}/${patch_file}). It's not very handy if the package is not your own. 通过将补丁直接添加到带有软件包描述($ {buildroot_root_dir} / package / $ {packagename} / $ {patch_file})的文件夹中。 如果包装不是您自己的，那不是很方便。
- By using the directory with global patches. In this case, the patches are stored in a separate folder in my external-tree. 通过将目录与全局补丁一起使用。 在这种情况下，补丁存储在我的外部树的单独文件夹中。
It's the second method that I'll use. The path to the global folder is set in the section Build options → global patch directories. You can set multiple directories. Note that to apply patches to the kernel, it's recommended to use the item Kernel → custom kernel patches. There, you can specify a list of patches as an URL or path to a file/catalog. You can apply a patch to a single version of the package, or all versions. The difference in the path to the patch:
这是我要使用的第二种方法。 全局文件夹的路径在构建选项→全局补丁程序目录部分中设置。 您可以设置多个目录。 请注意，要将补丁程序应用到内核，建议使用项目内核→自定义内核补丁程序。 在此处，您可以将修补程序列表指定为URL或文件/目录的路径。 您可以将修补程序应用于包的单个版本或所有版本。 补丁路径的区别：
- <global-patch-dir>/<packagename>/<packageversion>/ — apply a patch to a specific version of the package. <global-patch-dir> / <packagename> / <packageversion> /-将补丁应用于特定版本的软件包。
- <global-patch-dir>/<packagename> overlay the package on all versions of the package. <global-patch-dir> / <packagename>在所有版本的软件包上覆盖该软件包。
包依赖 (Package dependencies)
The important point is to describe the package dependency. It's described in two files: Config.in (Config.in. host for the hosting package) and ${packagename}.mk.
重要的是描述程序包的依赖性。 它在两个文件中进行了描述：Config.in(用于托管程序包的Config.in。host)和$ {packagename} .mk。
File Config.in (like Config.in.host) adds the package to the KConfig menu. You can set two types of dependencies: depends on and select.
File Config.in(如Config.in.host)会将程序包添加到KConfig菜单。 您可以设置两种类型的依赖关系：取决于和选择。
Depends on — displays the package in the menu only if the specified dependencies are already enabled.
取决于-仅在已启用指定的依赖性的情况下，才在菜单中显示程序包。
Select works the other way around: if our package is selected, enable the dependency. Both these dependencies work to generate the build configuration (the .config file in the Buildroot root).
Select以另一种方式起作用：如果选择了我们的包，请启用依赖项。 这两个依赖项都可以用来生成构建配置(Buildroot根中的.config文件)。
The dependency in the ${packagename}.mk file works differently. During the build stage, Buildroot generates a list of packages to build and install in alphabetical order. And it may happen that, to build a package Apackage, you need a Bpackage package, which will be built, but too late. An error occurs that stops the build.
$ {packagename} .mk文件中的依赖项的工作方式有所不同。 在构建阶段，Buildroot会生成要按字母顺序构建和安装的软件包列表。 可能会发生，要构建Apackage包，您需要一个Bpackage包，该包将被构建，但为时已晚。 发生错误，停止构建。
So, to the file Apackage.mk you need to add this line:
因此，需要在文件Apackage.mk中添加以下行：
APACKAGE_DEPENDENCIES = BPACKAGEWhen the Buildroot reaches the Apackage build and sees the dependency, it'll first build the Bpackage package, and then return to Apackage.
当Buildroot到达Apackage构建并看到相关性时，它将首先构建Bpackage软件包，然后返回Apackage。
变量和命令 (Variables and commands)
When writing a make-file with the package build/install rules, you can use variables. The following variables helped me:
当使用软件包构建/安装规则编写make-file时，可以使用变量。 以下变量对我有帮助：
- $(@D) — the path to the package’s build directory (for example, output/build/demopackage) $(@ D)-包的构建目录的路径(例如，output / build / demopackage)
- $TOPDIR — the root directory of the Buildroot $ TOPDIR — Buildroot的根目录
- $BASEDIR — the directory output $ BASEDIR —目录输出
- \$HOST_DIR, \$STAGING_DIR, \$TARGET_DIR — host fs, staging fs, and target fs build directories \ $ HOST_DIR，\ $ STAGING_DIR，\ $ TARGET_DIR-主机fs，暂存fs和目标fs构建目录
- $BUILD_DIR — the directory with unpacked and assembled packages $ BUILD_DIR —包含解包和组合包的目录
If you run make help in the Buildroot root, you can learn about additional commands:
如果在Buildroot根目录中运行make help，则可以了解其他命令：
Package-specific:
<pkg> - Build and install <pkg> and all its dependencies
<pkg>-source - Only download the source files for <pkg>
<pkg>-extract - Extract <pkg> sources
<pkg>-patch - Apply patches to <pkg>
<pkg>-depends - Build <pkg>'s dependencies
<pkg>-configure - Build <pkg> up to the configure step
<pkg>-build - Build <pkg> up to the build step
<pkg>-show-info - generate info about <pkg>, as a JSON blurb
<pkg>-show-depends - List packages on which <pkg> depends
<pkg>-show-rdepends - List packages which have <pkg> as a dependency
<pkg>-show-recursive-depends - Recursively list packages on which <pkg> depends
<pkg>-show-recursive-rdepends - Recursively list packages which have <pkg> as a dependency
<pkg>-graph-depends - Generate a graph of <pkg>'s dependencies
<pkg>-graph-rdepends - Generate a graph of <pkg>'s reverse dependencies
<pkg>-dirclean - Remove <pkg> build directory
<pkg>-reconfigure - Restart the build from the configure step
<pkg>-rebuild - Restart the build from the build step钩子 (Hooks)
You can add your hooks at different stages of the package build (from downloading to installation). For a complete list, see the Buildroot documentation.
您可以在软件包构建的不同阶段(从下载到安装)添加挂钩。 有关完整列表， 请参阅Buildroot文档 。
For example, after installing the demopackage package, I want to run a command that copies the README from the build directory to target-fs. To do this, I make changes to demopackage.mk:
例如，在安装demopackage软件包后，我想运行一个命令，将自述文件从构建目录复制到target-fs。 为此，我对demopackage.mk进行了更改：
vim package/demopackage/demopackage.mkFirst, I’ll set the section with the necessary commands
首先，我将用必要的命令设置该部分
define DEMOPACKAGE_COPY_README
cp $(@D)/readme.txt $(TARGET_DIR)/var/demopackage/
endefAnd now, I'll add these commands to execute in the post-install-target hook, which are executed after installing the package in target-fs:
现在，我将添加以下命令以在post-install-target钩子中执行，这些命令是在将软件包安装在target-fs中后执行的：
DEMOPACKAGE_POST_INSTALL_TARGET_HOOKS += DEMOPACKAGE_COPY_READMEThis example is very artificial. I recommend paying attention to the section of the article, where I ported the Zabbix package, there is a real application.
这个例子是非常人为的。 我建议您注意本文中移植Zabbix软件包的部分，这里有一个实际的应用程序。
将包添加到覆盖 (Adding a package to the overlay)
For convenience, I keep all my developments in the overlay, which is easy to connect to the Buildroot. Read more here
为了方便起见，我将所有开发都保留在叠加层中，可以轻松连接到Buildroot。 在这里阅读更多
Let's look at the file structure in the overlay that is necessary for adding packages (only the necessary ones are shown):
让我们看一下叠加中添加包所必需的文件结构(仅显示必要的包)：
../overlay/
├── package
│ ├── rodos
│ │ ├── 0001-MAKEFILE-FIX.patch
│ │ ├── Config.in
│ │ └── rodos.mk
│ └── zabbix
│ ├── Config.in
│ ├── zabbix-agent.service
│ ├── zabbix.hash
│ ├── zabbix.mk
│ └── zabbix-server.service
├── external.mk
├── Config.inPackage — the catalog with the packages themselves. There are 2 required files inside — Config.in and ${packagename}.mk. The first is responsible for displaying the KConfig package when configuring the Board; the second contains commands for building the package. It's also helpful to have a ${packagename}.hash file, which contains the hash of the archive with the package sources.
软件包-包含软件包本身的目录。 内部有2个必需文件-Config.in和$ {packagename} .mk。 第一个负责在配置Board时显示KConfig程序包； 第二个包含用于构建软件包的命令。 拥有$ {packagename} .hash文件也很有帮助，该文件包含带有包源的存档的哈希。
移植RODOS (Porting RODOS)
The practical part will start with a relatively simple package for the RODOS-5 thermal sensor. The source code is stored on the manufacturer's website as an archive. To start, I will create the necessary files:
实际部分将从相对简单的RODOS-5热传感器包装开始。 源代码作为存档存储在制造商的网站上。 首先，我将创建必要的文件：
../overlay/
├── package
│ ├── rodos
│ │ ├── 0001-MAKEFILE-FIX.patch
│ │ ├── Config.in
│ │ └── rodos.mkConfig.in — the file from which the menu will be built.
Config.in-从中构建菜单的文件。
[alexey@comp monitor]$ cat overlay/package/rodos/Config.in
config BR2_PACKAGE_RODOS
bool "rodos"
select BR2_PACKAGE_LIBUSB
help
rodos 5-6 usb termometer software- The first line specifies the variable associated with the package. 第一行指定与包关联的变量。
- The second sets the type of variable. In my case, this is a Boolean variable. If you add a package to the Board configuration, its value will be equal to y. String variables are also often used for string parameter tasks (for example, paths). 第二个设置变量的类型。 就我而言，这是一个布尔变量。 如果将软件包添加到Board配置中，则其值将等于y。 字符串变量也经常用于字符串参数任务(例如，路径)。
- The third adds the LIBUSB package if the RODOS package is being built. 如果正在构建RODOS软件包，则第三个添加LIBUSB软件包。
- The word help is followed by strings with help output on request. 单词help后面是带有请求的帮助输出的字符串。
################################################################################
#
# rodos 5 6
#
################################################################################
RODOS_SOURCE = RODOS5_6.tar.gz
RODOS_SITE = https://silines.ru/software/RODOS/RODOS-5_6
RODOS_DEPENDENCIES += libusb host-libusb
define RODOS_INSTALL_TARGET_CMDS
$(INSTALL) -D -m 0755 $(@D)/RODOS5_6 $(TARGET_DIR)/usr/bin/RODOS5_6
endef
define RODOS_BUILD_CMDS
$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) CFLAGS="$(TARGET_CFLAGS)" -C $(@D)
endef
$(eval $(generic-package))IMPORTANT The names of the set variables must match the package name. In this case, RODOS. This package is simple; let's look at the structure:
重要说明设置变量的名称必须与程序包名称匹配。 在这种情况下，为RODOS。 这个包很简单； 让我们看一下结构：
The last line, \$(eval $(generic-package)), sets the package type. In this case, we'll have to set the commands for building and installing the package ourselves. In the case of a cmake package (for example), these commands would follow the rules of the cmake file in the package.
最后一行\ $(eval $(generic-package))设置程序包类型。 在这种情况下，我们必须设置用于自行构建和安装软件包的命令。 在使用cmake软件包的情况下(例如)，这些命令将遵循软件包中cmake文件的规则。
RODOS_SOURCE — the name of the archive that will be downloaded. If you don't specify it, Buildroot will generate the archive name for downloading by its own rules. RODOS_SITE — the address of the source with source codes. In this case, it's the website address, but it can also be the address of ftp, git, gitlab, svn, and others. RODOS_DEPENDENCIES — the dependencies required for building the package.
RODOS_SOURCE —将要下载的档案的名称。 如果未指定，则Buildroot将生成存档名称，供其根据自己的规则进行下载。 RODOS_SITE —带有源代码的源地址。 在这种情况下，它是网站地址，但也可以是ftp，git，gitlab，svn等的地址。 RODOS_DEPENDENCIES —构建程序包所需的依赖项。
define RODOS_INSTALL_TARGET_CMDS — the section with commands that are used to install the collected files in target-fs.
定义RODOS_INSTALL_TARGET_CMDS —带有用于在target-fs中安装收集的文件的命令的部分。
define RODOS_BUILD_CMDS — commands with package compilation rules. It's important to pay attention to the use of variables.
定义RODOS_BUILD_CMDS —带有程序包编译规则的命令。 注意变量的使用很重要。
Special attention should be paid to the 0001-MAKEFILE-FIX.patch file. As previously mentioned, Buildroot can apply patches to packages. In this case, I put the patch directly in the package directory. Between unpacking and building a package, the system applies patches in alphabetical order.
应特别注意0001-MAKEFILE-FIX.patch文件。 如前所述，Buildroot可以将补丁应用于软件包。 在这种情况下，我将补丁直接放在包目录中。 在拆包和构建包装之间，系统将按字母顺序应用补丁。
添加Zabbix软件包 (Adding the Zabbix package)
The ZABBIX package turned out to be more difficult to port. The package is complex and requires dependency. Below is the version that works. This version not in builroot master branch, but already submitted. It's mandatory to set zabbix-agent; zabbix-server if necessary.
事实证明，ZABBIX软件包更难移植。 该程序包很复杂，需要依赖。 以下是有效的版本。 此版本不在builroot master分支中，但已提交。 必须设置zabbix-agent； zabbix-server(如果需要)。
So first, I created the package structure:
因此，首先，我创建了包结构：
tree overlay/package/zabbix/
overlay/package/zabbix/
├── Config.in
├── zabbix-agent.service
├── zabbix.hash
├── zabbix.mk
└── zabbix-server.serviceTo Config.in and make-file files with the build rules were added the following files:
向具有构建规则的Config.in和生成文件文件中添加了以下文件：
zabbix.hash This is the file with the checksum of the source archive
zabbix.hash这是带有源档案的校验和的文件
cat overlay/package/zabbix/zabbix.hash
# Locally computed
sha256 22bb28e667424ad4688f47732853f4241df0e78a7607727b043d704ba726ae0e zabbix-4.4.6.tar.gz
sha256 a823e00bc7f0844874f90fee97136f178e7debc76bace5f09e15ee8ed55f04c3 READMEThe first line indicates that the checksums were not taken from the manufacturer, but calculated independently.
第一行表明校验和不是从制造商那里获取的，而是独立计算的。
The next 2 lines give the checksums themselves: for the source file and the license file (located inside the source files). This is the requirement of Buildroot itself.
接下来的两行给出校验和本身：源文件和许可证文件(位于源文件内部)。 这是Buildroot本身的要求。
zabbix-agent.service, zabbix-server.service — systemd- the units for starting the agent and server.
zabbix-agent.service，zabbix-server.service -systemd-用于启动代理和服务器的单元。
Let’s look inside the Config.in:
让我们看一下Config.in：
cat overlay/package/zabbix/Сonfig.in
config BR2_PACKAGE_ZABBIX
bool "zabbix"
# Zabbix requires glibc, musl; any other alternative won't work
# If the condition is not met, the package won't be shown in the Board settings menu
depends on BR2_TOOLCHAIN_USES_GLIBC=y || BR2_TOOLCHAIN_EXTERNAL_GLIBC=y || BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
# Adds the pcre package to the system
select BR2_PACKAGE_PCRE
help
Zabbix is an enterprise-class open source distributed
monitoring solution. Zabbix is free of cost. Zabbix
is written and distributed under the GPL General Public
License version 2.
# if glibc is not used, a warning about its necessity is displayed
if (!BR2_TOOLCHAIN_USES_GLIBC && !BR2_TOOLCHAIN_EXTERNAL_GLIBC && !BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC)
comment "zabbix need glibc"
endif
# If the zabbix package is selected for the build
if BR2_PACKAGE_ZABBIX
# Similar to glibc, but only for zabbix-server
if (!BR2_PACKAGE_POSTGRESQL && !BR2_PACKAGE_MYSQL)
comment "zabbix server needs postgresql or mysql support"
endif
config BR2_PACKAGE_ZABBIX_SERVER
bool "zabbix server"
# this way, you can select one of the dependencies
depends on BR2_PACKAGE_POSTGRESQL || BR2_PACKAGE_MYSQL
select BR2_PACKAGE_ZLIB
select BR2_PACKAGE_LIBEVENT
# If the server is selected for the build
if BR2_PACKAGE_ZABBIX_SERVER
# This way, you can select one of the options
choice
prompt "server database backend"
config BR2_PACKAGE_ZABBIX_SERVER_MYSQL
bool "mysql"
depends on BR2_PACKAGE_MYSQL
config BR2_PACKAGE_ZABBIX_SERVER_POSTGRESQL
bool "postgresql"
depends on BR2_PACKAGE_POSTGRESQL
endchoice
# This is optional. After this, you can use the variable
BR2_PACKAGE_ZABBIX_SERVER_COPY_DUMPS
# during the building process. For example, you can call a hook at a certain value of this variable.
if BR2_PACKAGE_ZABBIX_SERVER_POSTGRESQL || BR2_PACKAGE_ZABBIX_SERVER_MYSQL
config BR2_PACKAGE_ZABBIX_SERVER_COPY_DUMPS
bool "install sql dumps"
help
Copy initial database dumps to /usr/zabbix/
endif
# This part is the requirements for the server's web interface.
if (!BR2_PACKAGE_PHP || (!BR2_PACKAGE_PHP_EXT_MYSQLI && !BR2_PACKAGE_PHP_EXT_PGSQL) || \
!BR2_PACKAGE_PHP_EXT_MBSTRING || !BR2_PACKAGE_PHP_EXT_BCMATH || \
!BR2_PACKAGE_PHP_EXT_SOCKETS || !BR2_PACKAGE_PHP_EXT_GD || \
!BR2_PACKAGE_PHP_EXT_LIBXML2 || !BR2_PACKAGE_PHP_EXT_CTYPE || \
!BR2_PACKAGE_PHP_EXT_SESSION || !BR2_PACKAGE_PHP_EXT_XMLREADER || \
!BR2_PACKAGE_PHP_EXT_XMLWRITER )
comment "zabbix-frontend need php with extensions(bc, sockets, "
comment "mbstring, gd, libxml2, ctype, session, xmlreader, xmlwriter, mysql or postgresql"
endif
choice
prompt "server ssl/tls backend"
config BR2_PACKAGE_ZABBIX_SERVER_NOTLS
bool "none"
config BR2_PACKAGE_ZABBIX_SERVER_OPENSSL
bool "openssl"
depends on BR2_PACKAGE_OPENSSL
config BR2_PACKAGE_ZABBIX_SERVER_GNUTLS
bool "gnutls"
depends on BR2_PACKAGE_GNUTLS
endchoice
# also optional. These variables will also be used during the build.
# allows you to change the list of dependencies, build rules, call hooks, and redefine them.
# commands for different build stages.
config BR2_PACKAGE_ZABBIX_SERVER_OPENIPMI
bool "openipmi support"
select BR2_PACKAGE_OPENIPMI
config BR2_PACKAGE_ZABBIX_SERVER_LIBSSH2
bool "libssh2 support"
select BR2_PACKAGE_LIBSSH2
config BR2_PACKAGE_ZABBIX_SERVER_LDAP
bool "openldap support"
select BR2_PACKAGE_OPENLDAP
if (!BR2_USE_MMU)
comment "netsnmp support need MMU"
endif
config BR2_PACKAGE_ZABBIX_SERVER_NETSNMP
bool "net-snmp support"
depends on BR2_USE_MMU # netsnmp
select BR2_PACKAGE_NETSNMP
config BR2_PACKAGE_ZABBIX_SERVER_LIBCURL
bool "libcurl support"
select BR2_PACKAGE_LIBCURL
config BR2_PACKAGE_ZABBIX_SERVER_LIBXML2
bool "libxml2 support"
select BR2_PACKAGE_LIBXML2
# Copying files for the web interface. Many dependencies with complex rules. depends on adds a load on the developer since you need to manually set all the necessary Board settings. At the same time, it guarantees the accuracy of settings and the presence of these packages in the built system.
config BR2_PACKAGE_ZABBIX_SERVER_COPY_FRONTEND
bool "copy php-frontend to target"
depends on BR2_PACKAGE_PHP
depends on BR2_PACKAGE_PHP_EXT_MYSQLI || BR2_PACKAGE_PHP_EXT_PGSQL
depends on BR2_PACKAGE_PHP_EXT_BCMATH
depends on BR2_PACKAGE_PHP_EXT_SOCKETS
depends on BR2_PACKAGE_PHP_EXT_MBSTRING
depends on BR2_PACKAGE_PHP_EXT_GD
depends on BR2_PACKAGE_PHP_EXT_LIBXML2
depends on BR2_PACKAGE_PHP_EXT_CTYPE
depends on BR2_PACKAGE_PHP_EXT_SESSION
depends on BR2_PACKAGE_PHP_EXT_XMLREADER
depends on BR2_PACKAGE_PHP_EXT_XMLWRITER
help
copy web-frontend to /usr/zabbix/php-frontend
endif
endifHow it looks in the menu:
菜单中的外观：
[*] zabbix
[*] zabbix server
server database backend (postgresql) --->
[ ] install sql dumps (NEW)
*** zabbix-frontend need php with extensions(bc, sockets, ***
*** mbstring, gd, libxml2, ctype, session, xmlreader, xmlwriter, mysql or postgresql ***
server ssl/tls backend (none) --->
[ ] openipmi support (NEW)
[ ] libssh2 support (NEW)
[ ] openldap support (NEW)
[ ] net-snmp support (NEW)
[ ] libcurl support (NEW)
[ ] libxml2 support (NEW)And the choice of database (within the zabbix server database backend):
以及数据库的选择(在zabbix服务器数据库后端内)：
( ) Use mysql support
(X) Use postgresql supportThen, you'll need an explanation of what, how, and why I did it.
然后，您将需要说明执行此操作的方式，方式和原因。
zabbix — installing the Zabbix package. Initially, the agent is set, and if necessary, the server is set. zabbix server — installing the Zabbix server — an important point. The server requires a database (postgresql or mysql), but it may be on a different host. However, you'll need the package to build it. TK is a mandatory requirement; I added the option depends on.
zabbix-安装Zabbix软件包。 最初，设置代理，如果需要，则设置服务器。 zabbix 服务器 -安装Zabbix服务器-要点。 服务器需要一个数据库(PostgreSQL或mysql)，但是它可能在不同的主机上。 但是，您将需要软件包来构建它。 传统知识是一项强制性要求； 我添加的选项取决于 。
install sql dumps — this option allows you to copy the sql dumps needed to create a Zabbix database.
安装sql dumps-使用此选项，您可以复制创建Zabbix数据库所需的sql dumps。
ZABBIX can support various features, such as working with ldap, openipmi, and so on. For all this, it needs header files and/or a library of corresponding packages — openldap, openipmi.
ZABBIX可以支持各种功能，例如使用ldap，openipmi等。 为此，它需要头文件和/或相应软件包的库-openldap，openipmi。
Make-file with build instructions (note that the variable names start with the package name and match the variable names I used above):
带有构建指令的Make-file(请注意，变量名以包名开头并与我上面使用的变量名匹配)：
################################################################################
#
#zabbix
#
################################################################################
# Package version. This is important because it's used to build the file name for downloading
# Learn more here https://buildroot.org/downloads/manual/manual.html#generic-package-reference
ZABBIX_VERSION = 4.4.6
# Source where the source codes will be downloaded from
ZABBIX_SITE = https://sourceforge.net/projects/zabbix/files
# License type and file with it
ZABBIX_LICENSE = GPL-2.0
ZABBIX_LICENSE_FILES = README
# Dependencies
ZABBIX_DEPENDENCIES = pcre
# List of options for configuration and build.
ZABBIX_CONF_OPTS = --with-libpcre=$(STAGING_DIR)/usr/bin/ \
--enable-agent
# An interesting point is an example of using hooks.
# To change the configuration file, I need to run sed after installing the files.
# First, you need to declare a set of commands, then add their call to hooks.
# I'll declare the commands first. Note that the sed call is from the toolchain, not the system.
define ZABBIX_CLIENT_CHANGE_PIDFILE_LOCATION
$(SED) 's%\#\ PidFile=/tmp/zabbix_agentd.pid%PidFile=/run/zabbix/zabbix_agentd.pid%g' $(TARGET_DIR)/etc/zabbix_agentd.conf
endef
# And now I'll add this set of commands to the hook that is executed after installation in the target
ZABBIX_POST_INSTALL_TARGET_HOOKS += ZABBIX_CLIENT_CHANGE_PIDFILE_LOCATION
# Canonical method for installing systemd units and autorun them in multi-user.targer
# To add UNIT, just add the file name to the ZABBIX_SYSTEMD_UNITS variable
# For example, ZABBIX_SYSTEMD_UNITS += zabbix-agent.service
# First, I'll add the file to the list
ZABBIX_SYSTEMD_UNITS += zabbix-agent.service
# Then I'll install them.
define ZABBIX_INSTALL_INIT_SYSTEMD
$(foreach unit,$(ZABBIX_SYSTEMD_UNITS),\
$(INSTALL) -D -m 0644 $(ZABBIX_PKGDIR)/$(unit) $(TARGET_DIR)/usr/lib/systemd/system/$(unit) && \
mkdir -p $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants && \
ln -fs -r $(TARGET_DIR)/usr/lib/systemd/system/$(unit) $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants/$(unit)
)
endef
# This is the correct way to add a user to the system
define ZABBIX_USERS
zabbix -1 zabbix -1 !- /var/lib/zabbix - zabbix zabbix user
endef
# An example of using a variable from Config.in. If the server is selected for installation, the following steps are performed
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER),y)
# Adding another systemd unit-file
ZABBIX_SYSTEMD_UNITS += zabbix-server.service
# Adding build options to existing ones
ZABBIX_CONF_OPTS += --enable-server \
--with-libevent \
--with-libpthread=$(STAGING_DIR)/usr \
--with-zlib=$(STAGING_DIR)/usr
# Also, add the dependencies
ZABBIX_DEPENDENCIES += libevent zlib
# Using hooks again - adding another set of commands to the list
ZABBIX_POST_INSTALL_TARGET_HOOKS += ZABBIX_SERVER_CHANGE_PIDFILE_LOCATION
# Support for one of the options, particularly openipmi.
# I also check the value of the variable, add build options and dependencies, and call hooks
# Need openipmi in staging dir. Patch submitted in 2019.12.16
# Before this patch is enabled, use this crutch
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_OPENIPMI),y)
ZABBIX_CONF_OPTS += --with-openipmi=$(STAGING_DIR)/usr
ZABBIX_DEPENDENCIES += openipmi
ZABBIX_PRE_CONFIGURE_HOOKS += BR2_PACKAGE_ZABBIX_SERVER_OPENIPMI_FIX_LIBS
define BR2_PACKAGE_ZABBIX_SERVER_OPENIPMI_FIX_LIBS
if [ ! -f $(STAGING_DIR)/usr/lib/libOpenIPMI.so ]; then \
cp -rf $(TARGET_DIR)/usr/lib/libOpenIPMI* $(STAGING_DIR)/usr/lib/ ;\
cp -rf $(TARGET_DIR)/usr/include/OpenIPMI $(STAGING_DIR)/usr/include/ ;\
fi
endef
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_LIBCURL),y)
ZABBIX_CONF_OPTS += --with-libcurl=$(STAGING_DIR)/usr/bin/curl-config
ZABBIX_DEPENDENCIES += libcurl
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_LIBXML2),y)
ZABBIX_CONF_OPTS += --with-libxml2=$(STAGING_DIR)/usr/bin/xml2-config
ZABBIX_DEPENDENCIES += libxml2
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_NETSNMP),y)
ZABBIX_CONF_OPTS += --with-net-snmp=$(STAGING_DIR)/usr/bin/net-snmp-config
ZABBIX_DEPENDENCIES += netsnmp
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_LDAP),y)
ZABBIX_CONF_OPTS += --with-ldap=$(STAGING_DIR)/usr
ZABBIX_DEPENDENCIES += openldap
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_LIBSSH2),y)
ZABBIX_CONF_OPTS += --with-ssh2=$(STAGING_DIR)/usr
ZABBIX_DEPENDENCIES += libssh2
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_OPENSSL),y)
ZABBIX_CONF_OPTS += --with-openssl=$(STAGING_DIR)/usr
ZABBIX_DEPENDENCIES += openssl
else ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_GNUTLS),y)
ZABBIX_CONF_OPTS += --with-gnutls=$(STAGING_DIR)/usr
ZABBIX_DEPENDENCIES += gnutls
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_COPY_FRONTEND),y)
ZABBIX_POST_INSTALL_TARGET_HOOKS += ZABBIX_SERVER_COPY_FRONTEND
define ZABBIX_SERVER_COPY_FRONTEND
mkdir -p $(TARGET_DIR)/usr/zabbix/php-frontend/
cp -r $(@D)/frontends/php/* $(TARGET_DIR)/usr/zabbix/php-frontend/
endef
endif
define ZABBIX_SERVER_CHANGE_PIDFILE_LOCATION
$(SED) 's%\#\ PidFile=/tmp/zabbix_server.pid%PidFile=/run/zabbix/zabbix_server.pid%g' $(TARGET_DIR)/etc/zabbix_server.conf
endef
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_MYSQL),y)
ZABBIX_DEPENDENCIES += mysql
ZABBIX_CONF_OPTS += --with-mysql=$(STAGING_DIR)/usr/bin/mysql_config
# Need package/mariadb/0003-add-sysroot-path-to-mariadb_config.patch by Ryan Coe
# While this patch is not included, use this crutch
ZABBIX_PRE_CONFIGURE_HOOKS += ZABBIX_DISABLE_MARIADB_CONFIG
ZABBIX_POST_CONFIGURE_HOOKS += ZABBIX_ENABLE_MARIADB_CONFIG
define ZABBIX_DISABLE_MARIADB_CONFIG
if [ -f "$(STAGING_DIR)/usr/bin/mariadb_config" ]; then \
mv $(STAGING_DIR)/usr/bin/mariadb_config $(STAGING_DIR)/usr/bin/mariadb_config_save; \
fi
endef
define ZABBIX_ENABLE_MARIADB_CONFIG
if [ -f "$(STAGING_DIR)/usr/bin/mariadb_confi_save" ]; then \
mv $(STAGING_DIR)/usr/bin/mariadb_config_save $(STAGING_DIR)/usr/bin/mariadb_config; \
fi
endef
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_COPY_DUMPS),y)
ZABBIX_POST_INSTALL_TARGET_HOOKS += ZABBIX_SERVER_PREPARE_MYSQL
endif
define ZABBIX_SERVER_PREPARE_MYSQL
mkdir -p $(TARGET_DIR)/usr/zabbix/mysql_schema/
cp -r $(@D) $(@D)/database/mysql/*\.sql $(TARGET_DIR)/usr/zabbix/mysql_schema/
endef
endif
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_POSTGRESQL),y)
ZABBIX_DEPENDENCIES += postgresql
ZABBIX_CONF_OPTS += --with-postgresql=$(STAGING_DIR)/usr/bin/pg_config
define ZABBIX_SERVER_PREPARE_POSTGRESQL
mkdir -p $(TARGET_DIR)/usr/zabbix/postgresql_schema
cp -r $(@D)/database/postgresql/*\.sql $(TARGET_DIR)/usr/zabbix/postgresql_schema/
endef
ifeq ($(BR2_PACKAGE_ZABBIX_SERVER_COPY_DUMPS),y)
ZABBIX_POST_INSTALL_TARGET_HOOKS += ZABBIX_SERVER_PREPARE_POSTGRESQL
endif
endif
endif
# I set the package type. In this case, autotools will be used.
$(eval $(autotools-package))When installing the package, zabbix-agent and its dependencies will also be installed. The location of its pid-file will be changed, and the systemd UNIT file will be installed with its autorun in multi-user.target.
安装软件包时，还将安装zabbix-agent及其依赖项。 其pid文件的位置将被更改，系统化的UNIT文件将以其自动运行的方式安装在multi-user.target中。
Optionally, you can also install zabbix-server. But then DBMS will be selected for installation, and the dump files with initial data (optional), as well as the web-frontend files (also optional), will be copied to the target system.
您也可以选择安装zabbix-server。 但是随后将选择DBMS进行安装，并将带有初始数据的转储文件(可选)以及Web前端文件(也可选)复制到目标系统。
I specifically didn't add a web server installation. First, it can be located on another computer. Secondly, there are a lot of options for a web server; if you'll need it — you'll install the right one with the necessary php modules.
我特别没有添加Web服务器安装。 首先，它可以位于另一台计算机上。 其次，Web服务器有很多选择。 如果您需要它-您将安装必要PHP模块和正确的php模块。
结论 (Conclusion)
As you can see from the text above, it's quite possible to port packages to the Buildroot by yourself. There are powerful mechanisms that automate the build. At the same time, it's possible to intervene in the build process at any time and change the necessary moments.
从上面的文本中可以看到，您很有可能自己将软件包移植到Buildroot。 有强大的机制可以自动构建。 同时，可以随时干预构建过程并更改必要的时刻。
zabbix软件包
扫一扫
994
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
