-
Type:
Incident report
-
Resolution: Fixed
-
Priority:
Trivial
-
Affects Version/s: 3.0.0rc2
-
Component/s: Agent (G), Installation (I), Proxy (P), Server (S)
-
Environment:Windows, Microsoft Visual C++
One can spot the following piece in mbed tls library sources:
#ifdef _MSC_VER
#include <basetsd.h>
typedef UINT32 uint32_t;
#else
#include <stdint.h>
#endif
This conflicts with Zabbix definition:
#if defined(_WINDOWS)
# ifndef uint32_t
# define uint32_t __int32
# endif
#endif
...and forces us to #undef uint32_t on Windows before we include mbed tls headers, which makes the further use of uint32_t somewhat ambiguous.
I would like to suggest defining zbx_uint32_t properly (as we define zbx_uint64_t) and use a temporary #define uint32_t zbx_uint32_t while we make continuous effort to eliminate uint32_t from Zabbix code.