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
When building with the Android NDK it automatically adds a -DANDROID definition to {C/CXX}FLAGS and it can be used to nop calls to android_log on non-android targets.
Right now I'm building a library that sets up several appenders and I'm handling adding the AndroidAppender using the ANDROID definition shown below. It's a small point, but It would be nice to clean this up and push these conditions into the AndroidAppender. It would just be a nop if it's being run on a non-Android target.
I don't even think a compile warning is necessary if you're compiling in an AndroidAppender for a non-Android target.
I'm already handling the linking of plog/log using a cmake interface and there's two places I need to manage this. I guess this could get pushed into plog/CMakeLists.txt too?
When building with the Android NDK it automatically adds a -DANDROID definition to {C/CXX}FLAGS and it can be used to nop calls to android_log on non-android targets.
Right now I'm building a library that sets up several appenders and I'm handling adding the AndroidAppender using the ANDROID definition shown below. It's a small point, but It would be nice to clean this up and push these conditions into the AndroidAppender. It would just be a nop if it's being run on a non-Android target.
I don't even think a compile warning is necessary if you're compiling in an AndroidAppender for a non-Android target.
I'm already handling the linking of plog/log using a cmake interface and there's two places I need to manage this. I guess this could get pushed into
plog/CMakeLists.txt
too?The text was updated successfully, but these errors were encountered: