LOG_<LEVEL> macros conflicting with app macros

[vlahd]

Namely, I'm having issues with LOG_DEBUG and LOG_ERROR. These are very common names for logging macros and it's a small but annoying issue. Can they be prefixed with DILIGENT_ or some other naming convention?

Thank you!

[TheMostDiligent]

These macros are intended to only be used internally, they should not leak to the public API. Do you know what header causes the conflict?

[vlahd]

I'll track it down and update the ticket

[vlahd]

Sadly can't really find some good tools to help with this. So far I've tracked LOG_ERROR somehow leaking from #include <DiligentTools/TextureLoader/interface/TextureUtilities.h>. Not sure where LOG_DEBUG is coming from tho yet.

I'll write a quick script when I find some time to figure it out

[TheMostDiligent]

Yes, this header indeed leaks LOG_ERROR. Fixing it is not straightforward though, I would recommend just #undef LOG_ERROR as a temporary workaround.