Václav Haisman
Václav Haisman
I am guessing using different -std=c++XY should not matter much as long as you use the same version of GCC for all of the objects that linked together. (https://stackoverflow.com/questions/46746878/is-it-safe-to-link-c17-c14-and-c11-objects)
As for the flags, `./configure CXXFLAGS="-std=c++17"` should work, I think.
This looks like a MinGW issue. MinGW 6.3.0 seem rather old. Try with more current version, e.g., from .
I have no plans for this. Yes, a new Appender subclass would the right way to implement log4cplus → OpenTelemetry bridge.
There is not need for the `env:` prefix. Resolving placeholders from environment variables is the default.
It is possible. You just have to attach some `Appender` instance to some logger (usually the root logger) and you can start using the logger.
You can do that by redefining the `LOG4CPLUS_MACRO_FUNCTION()` function macro. The sequence should be something like this: ``` #include #undef LOG4CPLUS_MACRO_FUNCTION #define LOG4CPLUS_MACRO_FUNCTION() __FUNCTION__ ``` Undef and define the macro...
It is a macro, it is active where it is used. If you compile the code that uses the macro into a binary or a library, you can't change it...
You have to use it in the way I have shown: ``` #include #undef LOG4CPLUS_MACRO_FUNCTION #define LOG4CPLUS_MACRO_FUNCTION() __FUNCTION__ ``` You cannot do it any other way.
@davewichers I actually did experiment with it back in November. But I couldn't get it to do what Antisamy needs it to do. See https://github.com/nahsra/antisamy/compare/main...wilx:antisamy:transformer-experiment?expand=1