Replies: 1 comment
-
In theory Zabbix provides no binary compatibility guarantees. In practice their policies are inconsistent. Sometimes they avoid forcing users to re-build modules, sometimes they break modules without much hesitation. With some luck you may be able to use same module binary across multiple major versions. To facilitate that I try to stay within supported module API to avoid issues when Zabbix is absolutely entitled to break compatibility. But without any ABI stability guarantees Zabbix can break module compatibility even by repackaging same minor version with different compiler flags. To be safe, you should probably compile module for each minor Zabbix version. At least, that's what automated module build pipeline will likely do. Ideally, you should even match compiler flags used to build Zabbix. You may ask, what to do if you use Zabbix packages. I don't have a good answer for that... |
Beta Was this translation helpful? Give feedback.
-
Do I have to compile a new module for each minor or each major version?
Beta Was this translation helpful? Give feedback.
All reactions