Closed chefhoobajoob closed 9 years ago
I can get a clean build by adding #include to inet.hpp, though I'm not sure that's your preferred fix.
Do you mean adding something like #include <cstdint>
to inet.hpp
?
Yes - looks like I failed to use markdown correctly for <cstdint>
.
I believe adding this is totally a good fix, yes.
Since I do not have that problem on Linux, out of curiosity, which cpp
file was triggering the build error? (Or maybe this is related to precompiled header?)
message.cpp - I think it's the only implementation file using it (for serialization, I believe).
I downloaded the latest source tree and have my own vs solution and project files I use to build windows libs. When I run that build, I find that inet.hpp (and only this file) produces errors on all occurrences of uintxx_t types.
I can get a clean build by adding
#include <cstdint>
toinet.hpp
, though I'm not sure that's your preferred fix.