You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into a conflict when including the NORM library (actually the protolib submodule) into my own project.
Both the NORM library (via protoDebug.h) and my project are using PLOG for logging. Both are defining logging macros, such as PLOG_INFO, but they use different log levels (e.g., ProtoDebugLevel vs. plog::Severity). This results in a type mismatch when the PLOG_INFO macro is expanded.
My suggestion would be to wrap the macros in a distinct namespace. This way, when you include both PLOG and protoDebug, you can explicitly refer to which logging system you are using.
The text was updated successfully, but these errors were encountered:
Ry-Kode
changed the title
PLOG conflict with protoDefs
PLOG conflict with protoDebug
Sep 14, 2024
Hello,
Thank you for sharing your excellent work!
I ran into a conflict when including the NORM library (actually the protolib submodule) into my own project.
Both the NORM library (via protoDebug.h) and my project are using PLOG for logging. Both are defining logging macros, such as PLOG_INFO, but they use different log levels (e.g., ProtoDebugLevel vs. plog::Severity). This results in a type mismatch when the PLOG_INFO macro is expanded.
My suggestion would be to wrap the macros in a distinct namespace. This way, when you include both PLOG and protoDebug, you can explicitly refer to which logging system you are using.
The text was updated successfully, but these errors were encountered: