-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.33.1 does not compile with -DBUILDEASYLOGGINGPP=OFF #6009
Comments
Thanks so much for your report and details of your workaround! I considered how best to label this discussion for the attention of the RealSense team. easyloggingpp is already a part of the SDK via its 'third-party' folder, so 'feature request' is not appropriate as it already exists. On the basis that easyloggingpp is an existing part of the SDK that worked before and now does not work for you without manual code changes according to your report, I will label it as "bug". I hope that this approach works for you. |
Sure, I just forgot the label - thanks! |
So if I wanna use easyloggingpp with the rs lib at the same time, is there any workaround now? The easyloggingpp is really useful and convenient. |
@7oud The listed Known Issue in the SDK release notes regarding problems using easyloggingpp is named to be with the 2.33.1 SDK version specifically. I don't know if anyone has tested easyloggingpp with newer SDK versions to see whether the problem was isolated to just that one SDK version. |
@MartyG-RealSense In the latest v2.35.2 release note, #6009 is still in the known issues |
It looks like the "pull" to clear up issues so that the updated code can be merged into the SDK is still an ongoing project. |
Posting to keep this discussion open. |
Issue Description
Since 2.33.1, we cannot compile without easyloggingpp anymore. The reason is simple: In src/log.h, there is a new struct
log_message
in lines 11-17 defined within the preprocessor directive#if BUILD_EASYLOGGINGPP
. In src/rs.cpp this struct is then used in lines 1122-1207 outside this directive, resulting in compiler errors.Our quick fix was to wrap this part in the same preprocessor directive which compiles successfully. We did not investigate further if this causes any side effects, but so far everything works as expected.
Thank you,
Kind Regards,
Andreas
The text was updated successfully, but these errors were encountered: